iac.htora.dev · security templates

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

  1. Someone creates a pod: directly, or through a deployment.
  2. The admission controller checks it: privileged, host access, image signature.
  3. Refused, or allowed and reported: enforce or audit, per policy.
  4. The result reaches responders: as a policy report and an event.
PlatformUsesThe part that catches people
KubernetesKyverno installed by Argo CD, with keyless image signatures from GitHub ActionsKyverno skips kube-system and its own namespace by default, and the Standard policy excludes three namespaces.

Run the quick start

Check which clusterkubectl config current-context
Applykubectl apply -k .
Watch it synckubectl -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.

Read the full pageDownload PDF

Registry 0.23.0. Built 2026-11-17.

Made by Habibullah Tora. Source on GitHub. Code under the MIT licence, writing under CC BY 4.0.