update(event-generator): default configuration uses the "run" command

The event-generator is deployed using the "run" command which just generates activity without checking if Falco reacts to the events. This way, Falco does not need to expose the grpc socket. Signed-off-by: Aldo Lacuku <[email protected]>
MueChr · Jul 12, 2022 · c4b7054 · c4b7054
1 parent c6a1f71
commit c4b7054
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 3 deletions.
diff --git a/event-generator/README.md b/event-generator/README.md
@@ -32,7 +32,7 @@ In order to install the event-generator in a custom namespace run:
 kubectl create ns "ns-event-generator"
 helm install event-generator falcosecurity/event-generator --namespace "ns-event-generator"
 ```
-When the event-generator is installed using the default values in `values.yaml` file it is deployed using a k8s job, running the `test` command and, generates activity only for the k8s audit. 
+When the event-generator is installed using the default values in `values.yaml` file it is deployed using a k8s job, running the `run` command and, generates activity only for the k8s audit. 
 For more info check the next section.
 
 > **Tip**: List all releases using `helm list`, a release is a name used to track a specific deployment

diff --git a/event-generator/values.yaml b/event-generator/values.yaml
@@ -51,7 +51,7 @@ config:
   # run: runs actions.
   # test: runs and tests actions.
   # For more info see: https://github.com/falcosecurity/event-generator.
-  command: test
+  command: run
   # -- Regular expression used to select the actions to be run.
   actions: "^k8saudit"
   # -- Runs in a loop the actions.
@@ -63,6 +63,6 @@ config:
 
   grpc:
     # -- Set it to true if you are deploying in "test" mode.
-    enabled: true
+    enabled: false
     # -- Path to the Falco grpc socket.
     bindAddress: "unix:///var/run/falco/falco.sock"