Menu

CEL Admission Policies: Replacing Your Gatekeeper Webhooks With Native Kubernetes
πŸ“°

CEL Admission Policies: Replacing Your Gatekeeper Webhooks With Native Kubernetes

DEV Community: kubernetesΒ·Florient DOGBEΒ·7 days ago
#q9K2nRrX
#devtokubernetes#devto#dev#policy#namespace
Reading 0:00
15s threshold

Every admission webhook you install is a new single point of failure sitting on the critical path of every API write. Gatekeeper, Kyverno, OPA β€” they all work the same way: the kube-apiserver makes a synchronous HTTPS call to a pod, waits for an answer, and decides what to do when that call fails. ValidatingAdmissionPolicy (VAP) removes that call entirely. The policy is a CEL expression compiled and evaluated inside the API server. No pod, no service, no certificate, no timeout.

This article covers how to write real VAP policies, how to validate them with --dry-run=server and audit annotations, and how to move from Audit to Deny without taking production down on a Friday afternoon.

Why the webhook is the weakest link in your admission chain

A ValidatingWebhookConfiguration forces you into an uncomfortable trade-off through a single field: failurePolicy .

With failurePolicy: Fail , if the Gatekeeper pods are unschedulable, if the service's endpoints are empty, if the CA bundle has rotated out of sync, or…

Continue reading β€” create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.