# Kyverno enforces policy on Kubernetes resources at admission, and its own README limits it to Kubernetes

Facts read 16 Nov 2026. Page reviewed 16 Nov 2026.

Kyverno is an Apache 2.0 policy engine for Kubernetes that validates, mutates and generates resources at admission and scans existing ones. The CNCF project page read on 16 Nov 2026 lists it as graduated on 16 Mar 2026. Release v1.20.0 is latest, published 12 Nov 2026. Its CLI tests policies before they reach a cluster.

## Kyverno described by eight fields, read 16 Nov 2026

| Field | Value |
| --- | --- |
| What it evaluates | Kubernetes resources: validation, mutation, generation and image verification, plus background scans of existing resources |
| Where it runs | As an admission controller inside a cluster, and as a CLI for testing policies against resources before they are added to a cluster |
| Policy language | YAML policies (ClusterPolicy under kyverno.io/v1); the documentation also lists newer policy types such as ValidatingPolicy and a guide to migrating to CEL policies |
| Clouds and targets | Kubernetes clusters on any cloud. The README says Kyverno can only affect policies used by Kubernetes. Account-level guardrails for AWS, Azure or Google Cloud: none found on 16 Nov 2026 |
| License | Apache License 2.0 (LICENSE file, read 16 Nov 2026) |
| Maintainer | The Kyverno project, contributed by Nirmata. The CNCF page says graduated on 16 Mar 2026; the GitHub README read the same day still says incubating |
| Tested before enforcement | failureAction Audit records violations in a policy report and allows the request; Enforce blocks. The Kyverno CLI tests policies against resources |
| Current version | v1.20.0, marked Latest, released 12 Nov (the page shows no year; asset timestamps read 2026-11-11) |

## Kyverno governs what runs on clusters, not the cloud account that hosts them

Kyverno's README says it is "only able to impact the policies used by Kubernetes". It does not replace Kubernetes RBAC, and it complements the built-in ValidatingAdmissionPolicies and MutatingAdmissionPolicies with reporting, exception management and periodic background scanning. Companion projects, such as Kyverno JSON for non-Kubernetes JSON payloads, Chainsaw for end-to-end testing and Policy Reporter for violation reporting, are separate and have their own release cycles.

For this site that sets the boundary. A Kyverno policy can stop a privileged pod. It cannot stop an engineer attaching an IAM policy in AWS. The cloud-side entries in the [library](/library/) cover the second case.

## Audit mode and per-namespace overrides are the rollout path

Kyverno documents failureAction with two values. Enforce blocks the creation or update of a non-compliant resource. Audit allows it and logs a violation in a PolicyReport or ClusterPolicyReport. A policy in Audit mode also reports on existing resources during periodic scans. failureActionOverrides lets one policy enforce in one namespace and audit in another, as in the documentation's example where the default namespace enforces and the test namespace audits.

Kyverno also documents a behavior for existing violations: a newly created Enforce rule lets updates continue on resources that already violate it, unless validate.allowExistingViolations is set to false. The CLI page says it can validate and test policy behavior against resources before adding them to a cluster.

## The project states what it cannot do about Kubernetes itself

The README says Kyverno does not protect against vulnerabilities in the Kubernetes API server or the underlying infrastructure, and that its enforcement may be bypassed if Kubernetes itself has a security flaw. It also notes that the field spec.validationFailureAction is deprecated in favor of a per-rule failureAction, which affects policies copied from older examples.

## Kyverno belongs in the engine comparison for clusters only

Teams that run Kubernetes on AWS, Azure or Google Cloud often need both a cluster-level engine and the cloud's own guardrails. See [policy as code tools](/policy-as-code-tools/) for the field-by-field table, [policy as code examples](/policy-as-code-examples/) for a Kyverno ClusterPolicy from the project's documentation, and the [mechanisms](/mechanisms/scp/) that cover the account layer.

## Related pages

- [CloudFormation Guard: fields, version and testing](/engines/cloudformation-guard/)
- [AWS SCP examples explained: what each pattern blocks and breaks](/guides/aws-scp-examples-explained/)
- [How SCP evaluation works: allow lists, deny lists, and the limits](/guides/how-scp-evaluation-works/)
- [All of them](/guides/)

## Sources

- GitHub: kyverno/kyverno: https://github.com/kyverno/kyverno (read 16 Nov 2026)
- GitHub: Kyverno releases: https://github.com/kyverno/kyverno/releases (read 16 Nov 2026)
- GitHub: Kyverno LICENSE: https://raw.githubusercontent.com/kyverno/kyverno/main/LICENSE (read 16 Nov 2026)
- CNCF: Kyverno: https://www.cncf.io/projects/kyverno/ (read 16 Nov 2026)
- Kyverno: validate rules: https://kyverno.io/docs/writing-policies/validate/ (read 16 Nov 2026)
- Kyverno: CLI: https://kyverno.io/docs/kyverno-cli/ (read 16 Nov 2026)
- Kyverno: how Kyverno works: https://kyverno.io/docs/introduction/how-kyverno-works/ (read 16 Nov 2026)

Last reviewed 16 Nov 2026. Canonical: https://cloudgovernancetools.com/engines/kyverno/
