Kyverno
What is Kyverno?
KyvernoKyverno is a CNCF Kubernetes policy engine that validates, mutates, and generates resources using policies written as native Kubernetes YAML rather than a new DSL.
Kyverno installs as a Kubernetes admission webhook and evaluates ClusterPolicy or namespaced Policy custom resources written in YAML with match, exclude, validate, mutate, generate and verifyImages rules. Because a rule mirrors the structure of the Kubernetes object it governs, platform teams who already write manifests can author policy without learning OPA's Rego language — the main reason Kyverno is often chosen over OPA Gatekeeper for the same admission-control niche. Beyond blocking non-compliant objects, Kyverno can mutate them (inject a securityContext, add labels), generate dependent resources when a namespace appears (a default-deny NetworkPolicy, a RoleBinding), run background scans that report drift on already-admitted resources, and manage exception workflows.
A common hardening pattern is enforcing the Pod Security Standards (baseline/restricted) plus supply-chain controls: the verifyImages rule checks Cosign or Notation signatures and attestations before a pod is admitted, tying image provenance to deployment. Kyverno was created by Nirmata, contributed to the CNCF as a Sandbox project in November 2020, reached Incubating in July 2022, and graduated (the CNCF's top maturity tier) in March 2026 after a third-party security audit and governance review, with adopters including Bloomberg, Coinbase and LinkedIn. Recent releases add CEL-based policy types alongside the original engine. As cluster-admitting software with broad RBAC, the webhook itself is a high-value target and should be run with least privilege and monitored.
flowchart LR
USER[kubectl apply] --> API[kube-apiserver]
API -->|AdmissionReview| KV[Kyverno webhook]
KV --> V{validate / verifyImages}
V -->|fails rule| DENY[Request rejected]
V -->|passes| MUT[mutate: inject defaults]
MUT --> ADMIT[Object stored in etcd]
ADMIT -.generate.-> GEN[Create NetworkPolicy /<br/>RoleBinding in namespace]● Examples
- 01
A Kyverno policy that auto-generates a default-deny NetworkPolicy in every new namespace.
- 02
verifyImages policy requiring all container images to carry a valid Cosign signature.
● Frequently asked questions
What is Kyverno?
Kyverno is a CNCF Kubernetes policy engine that validates, mutates, and generates resources using policies written as native Kubernetes YAML rather than a new DSL. It belongs to the Cloud Security category of cybersecurity.
What does Kyverno mean?
Kyverno is a CNCF Kubernetes policy engine that validates, mutates, and generates resources using policies written as native Kubernetes YAML rather than a new DSL.
How do you defend against Kyverno?
Defences for Kyverno typically combine technical controls and operational practices, as detailed in the full definition above.
What are other names for Kyverno?
Common alternative names include: Kyverno Policy, ClusterPolicy.