Kyverno: Kubernetes Policy Engine Review
kyverno.io · checked 15 Oct 2026
Cloud-native Kubernetes policy engine for security, compliance, governance and automation.
How it plugs in
Signal on Kubernetes Security Software7.7#1 of 27
Kyverno is a Kubernetes-native policy engine operated in your own environment. Author policies with YAML or Common Expression Language to inspect, modify, create or remove resources, and check container signatures. Its CLI supports testing in continuous integration, while controllers enforce rules in a cluster. The project is free under the Apache License 2.0.

Review
In a line
Kyverno brings policy enforcement into Kubernetes as an open-source project. Platform teams can express rules as code for cluster objects and selected JSON inputs.
What it does
Policies can check resources, alter matching objects, create and synchronize resources, or schedule deletion. In Enforce mode, validation rejects noncompliant resources; Audit mode records the violations instead.
ImageValidatingPolicy and verifyImages rules can assess container signatures and attestations from Cosign or Notary authorities. Kubernetes PolicyReport objects record current pass and fail outcomes, while PolicyException objects allow selected policies to be exempted. The standalone CLI, also usable as a kubectl plugin, exercises policies against manifests before deployment.
How it connects
Install Kyverno in a Kubernetes cluster with Helm or YAML manifests; the project recommends Helm when customizing and upgrading production deployments. Its documentation also describes Helm, GitHub Actions and GitOps tools including ArgoCD.
Release downloads include CLI programs for Linux, macOS and Windows. Rules may inspect JSON inputs including Terraform, cloud resources and service-authorization data. A dedicated SDK and a separate API repository support developers building controllers or tools. Kyverno can help with Cloud Governance Software and Container Security Software use cases.
Good fit
Platform engineering groups can use Kyverno for shared Kubernetes checks covering security, compliance, automation and governance. YAML and Common Expression Language let teams author these controls without adopting another policy language.
Teams that want to evaluate manifests in continuous integration before applying them can use the CLI and its GitHub Actions workflows.
Watch for
Kyverno is run by the operator as admission and background controllers in a Kubernetes cluster. The admission controller is required in a standard installation; background, reports and cleanup controllers are optional. Production deployments should enable high availability with multiple replicas where supported.
By default, resource webhooks use fail-closed behavior. Consequently, a matching request may fail when the API server cannot contact Kyverno.
Pricing
The project is free software released under the Apache License 2.0. Both listed offerings are free, and no paid tier appears in the plans.
Verdict
Choose Kyverno if your organization runs Kubernetes and wants one self-hosted place to enforce rules, test them in CI, report results and verify image signatures. Familiar YAML and Common Expression Language authoring, plus Helm and GitOps support, align with common deployment workflows.
A hosted service may be a better choice if you do not want to operate controllers yourself, or if fail-closed admission behavior does not fit your availability requirements.
Our take
Kyverno suits organizations managing Kubernetes that need repeatable security, compliance and governance controls. The project brings admission checks, resource mutation and generation, cleanup, image verification and pre-deployment CLI testing together. Operating the controllers, planning high availability and handling fail-closed webhooks remain your responsibility. Organizations seeking a managed product or a simple standalone tool should look elsewhere.
- Free software under the Apache License 2.0
- Policies can be authored in YAML or Common Expression Language
- CLI tests manifests in CI before deployment
- Supports validation, mutation, generation and deletion of resources
- Checks Cosign and Notary image signatures
- Controllers must be operated in your Kubernetes cluster
- Webhooks use fail-closed behavior when the API server cannot reach Kyverno
- Production deployments should use high availability mode
- Pick it ifPlatform teams enforcing Kubernetes security and compliance; Teams testing policy changes in CI; Organizations using Helm or GitOps workflows
- Skip it ifYou need a hosted policy service instead of running Kubernetes controllers; Your environment cannot tolerate fail-closed admission webhooks; You depend on legacy policy types marked deprecated
Pricing
Kyverno is free and open source under the Apache License 2.0. No paid tier is listed.
- KyvernoOpen-source project · Apache License 2.0Free
- Open-source coreNo paid tier shown · Kubernetes policy engine · self-hosted deploymentFree
As github.com lists them, checked 4 Oct 2026.
Questions
Is Kyverno free?
Yes. The project is open source and distributed under Apache License 2.0, and the listed plans show no paid tier.
Where does Kyverno run?
Its admission and background controllers run in a Kubernetes cluster managed by the operator.
Which policy languages does Kyverno use?
You can author policies with YAML or Common Expression Language, without learning a separate Kyverno-specific language.
Can Kyverno test policies before deployment?
Yes. The CLI evaluates policies against Kubernetes manifests in continuous-integration workflows, including GitHub Actions.
What happens if Kyverno is unreachable?
Resource webhooks normally fail closed, meaning a matching request may be rejected when the API server cannot contact Kyverno.
Does Kyverno verify container images?
Yes. ImageValidatingPolicy and verifyImages rules can evaluate Cosign and Notary signatures and attestations.
How is Kyverno installed?
Installation is available through Helm or YAML manifests; Helm is the recommended choice for production customization and upgrades.