From 5193d8c6aa06d9ca395dddf9b00610ebbc89fce1 Mon Sep 17 00:00:00 2001 From: Niki Manoledaki Date: Wed, 7 Aug 2024 14:16:03 +0200 Subject: [PATCH] Delete comment about other Falco tests since they were added earlier Signed-off-by: nikimanoledaki --- docs/proposals/proposal-002-run.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/docs/proposals/proposal-002-run.md b/docs/proposals/proposal-002-run.md index 704ffb4..8373b1a 100644 --- a/docs/proposals/proposal-002-run.md +++ b/docs/proposals/proposal-002-run.md @@ -250,8 +250,6 @@ jobs: wait 15m - delete: | kubectl delete -f https://raw.githubusercontent.com/falcosecurity/cncf-green-review-testing/main/kustomize/falco-driver/ebpf/stress-ng.yaml # other Falco tests: - # - redis-test e.g. https://github.com/falcosecurity/cncf-green-review-testing/blob/main/kustomize/falco-driver/ebpf/redis.yaml - # - event-generator-test e.g. https://github.com/falcosecurity/cncf-green-review-testing/blob/main/kustomize/falco-driver/ebpf/falco-event-generator.yaml ``` The benchmark job has some test instructions/steps. In this case, it applies an upstream Kubernetes manifest. This manifest contains a `while` loop that runs `stress-ng`. The manifest already defines where the test should run in the cluster i.e. in which namespace. The functional unit test is time-bound in this case and scoped to 15 minutes. Therefore, we deploy this test, wait for 15 minutes, then delete the manifest to end the loop. The test steps depend on the functional unit of each CNCF project.