Kyverno Background Controller
Kyverno Background Controller is the background worker of Kyverno, the cloud-native policy engine for Kubernetes.
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.
78/100 Good
- Maintained
- 100last commit 4 days ago
- Popular
- 788,361 GitHub stars
- Easy to install
- 351 install platform, install notes, Docker image
- Light to run
- No data
Based on 3 of 4 factors.
Availability: platform listings confirmed today
- GitHub stars
- 8,361
- Open issues
- 722
- Last commit
- 2026-11-17
- Latest release
- v1.20.0
- License
- Apache-2.0
- Activity
- steady
Checked 3 days ago - source: GitHub (kyverno/kyverno)
Resources & Compatibility
ARM (e.g. Raspberry Pi) is supported.
Checked 54 days ago - source: Docker Hub image tags and published docs
First-install notes
- Add the Kyverno Helm repository Before installing, add the Kyverno Helm repository so Helm (a tool for installing Kubernetes apps) can download the official charts. If you skip this, Helm will not be able to find the Kyverno packages and installation fails. source
- Install the main Kyverno chart Install the main Kyverno chart into the kyverno namespace (a separate area in Kubernetes for these apps), which creates the core controller components and the place where policy checks run. Without it, the background controller has no running app to process work. source
- Install built-in policies if needed If you want ready-made rules, install the kyverno-policies chart into the same kyverno namespace after the main chart. Without this optional chart, Kyverno still runs, but you will not get its standard built-in policies. source
Fetched 53 days ago - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
Do I install kyverno-background-controller as a standalone Helm chart?
No. Install the main Kyverno chart into the kyverno namespace, which creates the core controller components and gives the background controller work to process.
How do I enable Kyverno's built-in policies with the background controller?
Add the Kyverno Helm repository and install the kyverno-policies chart into the same kyverno namespace after the main chart. Without that optional chart, Kyverno runs but does not include its standard built-in policies.
Why might the background controller fail to see CRDs installed after startup?
The background-controller lacks support for the --crdWatcher flag, and its RESTMapper cache is not invalidated after it starts and gains leader election. CRDs installed after the pod starts can remain invisible to it.
How can I test whether the background controller service account has required permissions?
Use kubectl auth can-i create helmrepositories --as system:serviceaccount:kyverno:kyverno-background-controller to check whether it can create Helm repositories.
Answers sourced from github.com, github.com, github.com, main.kyverno.io
Community
Collected 48 days ago - public community threads