reduce low priority Falco Slack alerts
Kube-bench CIS scan / Scan ephemeral K3s cluster (push) Successful in 1m4s
Kube-bench CIS scan / Scan ephemeral K3s cluster (push) Successful in 1m4s
This commit is contained in:
@@ -29,6 +29,8 @@ kubectl create secret generic falco-alerting \
|
||||
```
|
||||
|
||||
The `webhook-url` key is injected into Falcosidekick as `SLACK_WEBHOOKURL`.
|
||||
Falcosidekick sends only `WARNING` and higher priority events to Slack through
|
||||
`SLACK_MINIMUMPRIORITY`. Lower-priority events remain available in Falco logs.
|
||||
The Secret is intentionally not included in the Falco
|
||||
Kustomization because ArgoCD must not manage or render the credential from
|
||||
Git.
|
||||
|
||||
@@ -20,3 +20,7 @@ spec:
|
||||
secretKeyRef:
|
||||
name: falco-alerting
|
||||
key: webhook-url
|
||||
# Keep low-priority Falco events in cluster logs, but do not send
|
||||
# NOTICE-level activity to the Slack alert channel.
|
||||
- name: SLACK_MINIMUMPRIORITY
|
||||
value: warning
|
||||
|
||||
Reference in New Issue
Block a user