Home/Refreshers/Stop risky pods before they start: refresher
Stop risky pods before they start
Admission policies refuse privileged pods, host mounts, and unsigned images, and report every refusal.
Remember
- Someone creates a pod: directly, or through a deployment.
- The admission controller checks it: privileged, host access, image signature.
- Refused, or allowed and reported: enforce or audit, per policy.
- The result reaches responders: as a policy report and an event.
| Platform | Uses | The part that catches people |
|---|---|---|
| Kubernetes | Kyverno installed by Argo CD, with keyless image signatures from GitHub Actions | Kyverno skips kube-system and its own namespace by default, and the Standard policy excludes three namespaces. |
Run the quick start
| Check which cluster | kubectl config current-context |
| Apply | kubectl apply -k . |
| Watch it sync | kubectl -n argocd get applications |
Watch out
- Start in Audit mode and read the policy reports before enforcing.
- A signature proves where an image came from.
Check it worked
Try to create a privileged pod. In Audit mode it runs and a policy report lists it as failing. Once enforced, it is refused.