Kyverno
Kyverno is a Kubernetes-native policy engine that validates, mutates, and generates cluster resources using simple YAML rules, helping DevOps and platform…
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.
73/100 Good
- Maintained
- 99last commit 39 days ago
- Popular
- 788,244 GitHub stars
- Easy to install
- 150 install platforms, install notes
- Light to run
- No data
Based on 3 of 4 factors.
No GitHub repository data collected yet.
Resources & Compatibility
Requirements not published yet.
First-install notes
- Add Helm repo and install Kyverno Helm is a package tool for Kubernetes, so add the Kyverno Helm repo, create the kyverno namespace, and run the install command. This puts Kyverno in your cluster so it can check and enforce your rules on new workloads. source
- Check policies before applying Use `kyverno apply` with local policy and resource files to test rules before they run in the cluster. This helps you catch bad rules early, so you don’t accidentally block or reject workloads people need. source
Fetched 40 days ago - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
Does Kyverno replace Kubernetes RBAC for access control?
No, Kyverno works in conjunction with RBAC. RBAC controls access, while Kyverno enforces policy compliance and additional checks that RBAC cannot perform.
Can Kyverno protect against vulnerabilities in the Kubernetes API server?
No, Kyverno is designed for policy management and cannot address inherent Kubernetes security flaws. It cannot protect against API server vulnerabilities or underlying infrastructure flaws, and enforcement may be bypassed if Kubernetes itself has a security flaw.
What setup gotcha do people report with private registries?
A user reported trouble configuring Kyverno to enforce policies on a private Docker Hub registry. The thread says the documentation left the required steps unclear.
Can Kyverno express all complex policies as easily as Rego?
A community thread says Kyverno may be more limited than Rego-based policy for complex policy expressions. It compares Kyverno with OPA/Gatekeeper for Kubernetes policy enforcement.
Is Kyverno used alongside other Kubernetes security tools?
A community thread suggests using an OPA/Kyverno combination alongside tools like Trivy and Falco. This is in the context of open-source Kubernetes security tooling.
Answers sourced from github.com, www.reddit.com, www.reddit.com, www.reddit.com
Community
- Kubernetes Security tooling -Open Source (Non-SaaS - Reddit (reddit)
- Policy As Code on Kubernetes With Kyverno : r/kubernetes - Reddit (reddit)
- Help with Setting up Kyverno to Enforce Policies on a Private ... - Reddit (reddit)
- Anyone on AKS who using using Kyverno or another policy tool? - Reddit (reddit)
- Kubernetes Policy Management Tools Compared: OPA with ... - Reddit (reddit)
- Gatekeeper vs Kyverno : r/kubernetes - Reddit (reddit)
Collected 48 days ago - public community threads