The adoption of Kyverno solves the challenge of Policy-as-Code. However, a new question emerges for platform engineers: what happens when a slow policy rule adds latency? A slow admission webhook can degrade performance across the k8s cluster.
Tracing the webhook's lifecycle is the fastest way to pinpoint any bottlenecking rule.

The next step in your GitOps journey is to make your monitoring as declarative as your policies. In the live demo, you’ll learn how to monitor Kyverno's operational cycle using Prometheus, Tempo, and Grafana. We'll set SLOs and enable real-time alerts with observability as code, including metrics and alerts for policy failure rates or slow webhooks, and utilizing OpenTelemetry tracing to pinpoint what is causing a delay in the admission process.

If you manage policies as code, don't let silent performance bottlenecks threaten your cluster stability. Join to learn concrete steps needed to close your GitOps loop and achieve operational control over Kyverno.