# Kyverno Background Controller

Kyverno Background Controller is the background worker of Kyverno, the cloud-native policy engine for Kubernetes. It is open source and self-hosted, installable on Docker Hub and Kubernetes (Helm).

Canonical page: https://ourlocalhost.com/app/5533/kyverno-background-controller

## Description

Kyverno Background Controller is the background worker of Kyverno, the cloud-native policy engine for Kubernetes. It applies policies to resources that already existed in the cluster, runs cleanup for expired objects, and keeps ongoing compliance in the background. It is aimed at cluster operators who run Kyverno and want policies applied to existing workloads, not just newly created ones.

## Platform availability

Available on 1 of 10 platforms: Helm.

## Health score

78/100 (Good), based on 3 of 4 factors.
- Maintained: 100 (last commit 4 days ago)
- Popular: 78 (8,361 GitHub stars)
- Easy to install: 35 (1 install platform, install notes, Docker image)

## Links

- GitHub: https://github.com/kyverno/kyverno
- Docker Hub: https://hub.docker.com/r/cleanstart/kyverno-background-controller
- Kubernetes (Helm): https://artifacthub.io/packages/helm/kyverno/kyverno
- Documentation: https://kyverno.io/docs
- Official website: https://kyverno.io

## 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.

---
Source: Our Local Host (https://ourlocalhost.com/app/5533/kyverno-background-controller), the self-hosted and open-source app directory.
