| Use case | What Kyverno does | Main beneficiary |
| Namespace baseline and hygiene | Catches common misconfigurations, sets safe defaults, and sets a baseline RBAC and network posture | Operators |
| Certificate rotation | Triggers a rolling restart when a certificate is renewed | Developers |
| nodes/proxy hardening | Denies risky RBAC and verifies existing roles | Security |
| Change management gate | Allows Argo CD syncs only inside an approved window | Security and operators |
Certificate rotation. When a certificate is renewed, its Secret is updated in place. If the Secret is annotated for restart and names its workload, Kyverno’s background controller patches the pod template’s restartedAt annotation, and a rolling restart picks up the new certificate. No manual restart, and no expired certificate.
nodes/proxy hardening. A get permission on nodes/proxy looks read-only but reaches further than expected, by design upstream, so there is no CVE to wait for. One CEL ValidatingPolicy denies Roles and ClusterRoles that grant it, after Audit mode and a background scan verified existing roles. The denial message points to nodes/metrics or nodes/stats.
Change management gate. An approved change record opens a time-boxed window that closes itself. Every Argo CD sync is an update through the Kubernetes API, so Kyverno checks for an open, verified window at admission: inside it, the sync proceeds; outside it, the sync is denied with the reason. Force and replace syncs are blocked outright.
Every use case ships through Git and Argo CD, and starts in Audit.