document Falco runtime topology
Kube-bench CIS scan / Scan ephemeral K3s cluster (push) Successful in 1m0s
Kube-bench CIS scan / Scan ephemeral K3s cluster (push) Successful in 1m0s
This commit is contained in:
@@ -49,3 +49,9 @@ Falco workloads after the alerting integration is configured.
|
||||
The repository verifies Falco runtime detections locally. Webhook delivery is
|
||||
enabled by the Git-managed Falcosidekick resources after the Secret exists, and
|
||||
still requires an interactive Slack or Discord credential for end-to-end testing.
|
||||
|
||||
For runtime alert interpretation, see
|
||||
[`docs/runtime-detection.md`](../../docs/runtime-detection.md). The local k3d
|
||||
nodes share one Flatcar host kernel, so duplicate Falco notifications are
|
||||
possible. Separate VM nodes provide distinct kernels and are the more realistic
|
||||
production-style validation path.
|
||||
|
||||
Reference in New Issue
Block a user