# Falco settings. Kept in Git so a change to what the cluster watches for is a # pull request with an author on it. --- driver: # Needs kernel 5.8 or later and installs nothing on the host. Use kmod on # older kernels. kind: modern_ebpf # Rule updates are off on purpose. With them on, the rules running on your # cluster change whenever upstream publishes, and "why did this alert start # firing" stops having an answer. The rules that ship inside the Falco image # still load. falcoctl: artifact: install: enabled: false follow: enabled: false falco: json_output: true json_include_output_property: true log_level: info priority: notice # Mount the local rules ConfigMap into the folder Falco already reads. # Without these two lists the ConfigMap exists in the cluster and Falco never # sees it, which fails silently: no error, and no alerts from your rules. mounts: volumes: - name: local-rules configMap: name: falco-local-rules volumeMounts: - name: local-rules mountPath: /etc/falco/rules.d/local-rules.yaml subPath: local-rules.yaml readOnly: true # Where alerts go. Falcosidekick fans one event out to several destinations. falcosidekick: enabled: true replicaCount: 2 config: # The webhook URL usually carries a token, so it comes from a Secret you # create separately, outside this file. existingSecret: falco-alert-destinations webui: enabled: false resources: requests: cpu: 100m memory: 512Mi limits: memory: 1Gi # Falco has to run on every node, including nodes reserved for other # workloads. A node Falco skips is a node with no runtime visibility. tolerations: - operator: Exists