Home/Templates/See what containers are doing while they run
See what containers are doing while they run
Runtime alerts installed by the same pipeline that ships the workloads, so they cannot fall behind.
Argo CD
Why bother
Runtime security installed by hand drifts away from the cluster it is meant to watch, and disappears the next time the cluster is rebuilt. Shipping it through the same pipeline as everything else keeps them together.
Open a shell inside a pod. The alert should reach your SIEM.
How it works
Set it up
Pick your platform, then open the level you want. Each level is complete on its own. Read the comments in the files as you go. Anything with a real consequence is explained on the line where it happens.
Argo CD. Falco deployed by Argo CD, with rules kept in Git
What you need first
- A cluster where a privileged DaemonSet is permitted. Falco reads system calls, which is the whole point and also the trade.
- Kernel 5.8 or later for the eBPF driver. Older kernels need the kernel module instead.
- Somewhere for alerts to go. The Standard version expects a webhook in a Secret.
What it creates
- A falco namespace and a DaemonSet on every node
- Falcosidekick, which fans one alert out to several destinations
- A ConfigMap of local rules, synced from Git by Argo CD and mounted into every Falco pod (Standard)
See the two alerts this creates
The code
Quick startReady
kubectl config current-context
Shows which cluster kubectl is pointed at. Check it first.kubectl apply -f falco.yaml
Hands the Application to Argo CD.kubectl -n argocd get applications
Lists applications with their sync and health status.
Kubernetes schema passed
Last run 2026-10-02.
Open falco.yaml as plain text
StandardReady
- repoURL: https://github.com/your-org/your-cluster-config.gitapplication.yaml, line 38- repoURL: https://github.com/your-org/your-cluster-config.gitapplication.yaml, line 42
kubectl config current-context
Shows which cluster kubectl is pointed at. Check it first.kubectl apply -k .
Applies everything the kustomization lists, in order.kubectl -n argocd get applications
Lists applications with their sync and health status.
Kubernetes schema passedBuilds passed
Last run 2026-10-02.
Open application.yaml as plain text
Open kustomization.yaml as plain text
Open falco-local-rules.yaml as plain text
Open values.yaml as plain text
HardenedReady
kubectl config current-context
Shows which cluster kubectl is pointed at. Check it first.kubectl apply -k .
Applies everything the kustomization lists, in order.kubectl -n argocd get applications
Lists applications with their sync and health status.
Builds passed
Last run 2026-10-02.
Open kustomization.yaml as plain text
A rules ConfigMap does nothing on its own. Falco reads files from a folder, so the ConfigMap has to be mounted into that folder. Skip the mount and there is no error, and no alerts from your rules either. The Standard values.yaml mounts it.
With rule updates left on, the rules your cluster alerts on change whenever upstream publishes, and the question of why an alert started firing stops having an answer. The Standard version turns them off.
How to undo it
Delete the Application. The eBPF driver installs nothing on the host, so there is nothing left behind on the nodes.
What it costs
A pod per node, roughly 100m of CPU and 512Mi of memory each. The larger cost is usually the alert volume on the receiving side, which is why the Standard rules narrow the noisy defaults and keep them running.