Kubernetes API Explained
summary
Kubernetes API server splits incoming YAML handling into authentication (uses OpenID Connect), authorization, mutation admission controllers that can expand a 15-line manifest into ~150 lines (example: Istio sidecar injection), schema validation, and validation admission controllers that reject requests for bad certs or root containers. Validation and mutation support webhooks so external tools like Open Policy Agent enforce policies. Successful requests persist to the cluster datastore (etcd) and then actuators create or delete pods.
AI-written summary · about
