Course contentsShow
← Cloud and Infrastructure
Lesson 1405 of 2,98928. Kubernetes SecurityFree lesson

Admission Control Overview

Understanding admission controllers, their role in the API request lifecycle, and how they enforce policies before object persistence.

Admission Control Overview

What you'll learn: How Kubernetes admission controllers act as gatekeepers that intercept and validate API requests before objects are persisted to etcd.

What Are Admission Controllers?

Admission controllers are plugins that sit in the Kubernetes API server's request pipeline. They intercept every API request after authentication and authorization but before the object is written to etcd (the cluster's data store). Think of them as security checkpoints at an airport—you've proven who you are (authentication) and that you have permission to travel (authorization), but admission control checks whether your luggage meets safety requirements before you board.

The Request Lifecycle Position

When you create or modify a Kubernetes resource, the request flows through these stages:

  1. Authentication – Who are you?
  2. Authorization – Are you allowed to do this?
  3. Admission Control – Should this specific request be accepted? ← We are here
  4. Persistence – Write to etcd

Admission controllers enforce policies, set defaults, validate configurations, and can even modify requests on-the-fly.

Two Types of Admission Controllers

  • Validating controllers: Approve or reject requests based on rules (example: "No privileged pods allowed")
  • Mutating controllers: Modify requests before acceptance (example: "Inject a sidecar container automatically")

Some controllers do both. They run in order: mutating first, then validating.

Why They Matter for Security

Admission controllers enforce organization-wide policies that RBAC alone cannot. While RBAC says "Alice can create pods," admission controllers say "any pod created must meet these security standards"—regardless of who creates it. You've already seen the Pod Security Admission controller enforcing Pod Security Standards; that's admission control in action.

Key Takeaway: Admission controllers are policy enforcement engines that intercept API requests after authorization but before persistence, enabling cluster-wide security, compliance, and configuration management that goes beyond simple permission checks.