kyverno-policies

A collection of ready-made Kyverno policies that validate, mutate, and generate Kubernetes workloads and resources, helping operators enforce security,…

  • Infrastructure
  • Tools & Utilities
A collection of ready-made Kyverno policies that validate, mutate, and generate Kubernetes workloads and resources, helping operators enforce security, governance, and best practices across their clusters.

Platform availability

Available on 1 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

67/100 Good

Maintained
86last commit 17 days ago
Popular
54505 GitHub stars
Easy to install
251 install platform, install notes
Light to run
No data
Security check
85no serious findings, CI

Based on 4 of 5 factors.

Availability: platform listings confirmed today

GitHub stars
505
Open issues
245
Last commit
2026-11-04
License
Apache-2.0
Activity
rising

Checked 14 days ago - source: GitHub (kyverno/policies)

Resources & Compatibility

Requirements not published yet.

First-install notes

  • Install Kyverno with Helm into its own namespace Use the documented Helm commands (Helm is the Kubernetes package installer) to add the Kyverno repository, create a namespace (a named area in Kubernetes), and install Kyverno there. If you skip the repository or namespace, the install can fail or land somewhere unexpected. source
  • Test policies with kyverno apply first Use kyverno apply to check a policy against one workload file, a folder of workloads, or a cluster before making it live. This catches rule mistakes early so your policies don't reject or break running workloads. source
  • Optional: install CLI completion Installing CLI completion is optional, but it makes your terminal suggest kyverno commands as you type. It helps prevent typos when you are applying policies or running other Kyverno CLI commands. source
  • Requires Kyverno 1.17 or later These policies use the CEL-based policies.kyverno.io/v1 API and require Kyverno 1.17 or later; some individual policies may have additional requirements. source

Fetched 40 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

How are self-hosters managing Kyverno policies in their clusters?

Some teams deploy Kyverno with Helm and use a simple Helm template for policies, adding the entire policy to their values files.

What setup confusion do users report when enforcing Kyverno policies against a private Docker Hub registry?

Users report trouble understanding the required steps after going through the documentation.

What kind of policy guidance is provided for Kyverno PolicyExceptions?

A policy is provided to offer guardrails and rules that can help with scoping best practices.

Answers sourced from release-1-9-0.kyverno.io, www.reddit.com, www.reddit.com

Community

Collected 48 days ago - public community threads