Topic 3: Admission Webhooks
Official baseline: (The Kubernetes Authors, 2026b, 2026a). My working version: Admission webhooks let external code participate in API decisions at write time.
Mental Model
Admission webhooks let external code participate in API decisions at write time.
Notes
- They are powerful because every create/update path can depend on them.
- Availability, timeout, and failure policy need explicit design.
- Webhook outages can become cluster outages.
Homelab Angle
Treat webhooks as advanced platform code. Build strong observability before enforcing.
Verify It
- Read the object status before changing the manifest.
- Check events for the controller or node that is actually complaining.
- Confirm the official source linked below still matches the cluster version you run.
Common Failure Modes
- Treating the YAML object as the system, instead of one input to a reconciliation loop.
- Debugging from outside the cluster when the failure only exists inside cluster networking or node state.
- Forgetting that Kubernetes version, addon version, and runtime behavior are linked.
Sources
- Dynamic Admission Control - source path:
content/en/docs/reference/access-authn-authz/extensible-admission-controllers.md, commit 8cc9e19b8eec8d5cf49eacd66f86a81648edb1a0. - Admission Controllers - source path:
content/en/docs/reference/access-authn-authz/admission-controllers.md, commit 8cc9e19b8eec8d5cf49eacd66f86a81648edb1a0. - Kubernetes documentation is licensed under CC BY 4.0; these notes are original commentary and link back to the official source.
The Kubernetes Authors. (2026a). Admission Controllers. https://kubernetes.io/docs/reference/access-authn-authz/admission-controllers/
The Kubernetes Authors. (2026b). Dynamic Admission Control. https://kubernetes.io/docs/reference/access-authn-authz/extensible-admission-controllers/