Built-in Admission Controllers
What you'll learn: You'll discover what specific built-in admission controllers do and how they enforce essential policies automatically within your Kubernetes cluster.
What Are Built-in Admission Controllers?
Built-in admission controllers are pre-packaged policy enforcement plugins that come with Kubernetes. While you learned previously that admission controllers intercept API requests before objects are persisted, built-in controllers are the ready-to-use implementations that handle common operational needs. Think of them as pre-installed safety features in a car—they're there to prevent common mistakes before they become problems.
Common Built-in Admission Controllers
NamespaceLifecycle
This controller prevents you from creating objects in namespaces that don't exist or are being deleted. It's like a bouncer checking that the venue is still open before letting guests in. It also blocks deletion of system-critical namespaces like kube-system and default.
LimitRanger
LimitRanger enforces the resource constraints you define in LimitRange objects (which you learned about earlier). When a Pod is created without explicit requests/limits, this controller applies the defaults. It also validates that requested resources fall within acceptable ranges—rejecting Pods that ask for too much or too little.
ResourceQuota
This controller enforces the total resource consumption limits you set with ResourceQuota objects. It tracks namespace-level usage and rejects new objects if they would exceed quotas. Think of it as a budget manager ensuring teams don't overspend their allocated compute resources.
How They Work Together
These controllers often work in tandem. ResourceQuota ensures namespaces stay within budget, LimitRanger ensures individual Pods are properly sized, and NamespaceLifecycle ensures the namespace context is valid. They form layers of automated policy enforcement.
Key Takeaway: Built-in admission controllers like NamespaceLifecycle, LimitRanger, and ResourceQuota provide automatic, policy-driven validation that prevents common configuration errors and enforces resource governance without manual intervention.