How the Kubernetes API server processes requests: authentication, authorization, admission control, and storage.
How the Kubernetes API server processes requests: authentication, authorization, admission control, and storage.
Every kubectl or controller request flows through: Authentication (who are you? — certs, tokens, OIDC), Authorization (are you allowed? — RBAC), Admission Controllers (mutating + validating webhooks, OPA, Kyverno), then storage to etcd. The API server is stateless — all state is in etcd.
Key takeaways
Related concepts
Explore topics that connect to this one.
Ready to see how this works in the cloud?
Switch to Career Paths for structured paths (e.g. Developer, DevOps) and provider-specific lessons.
View role-based pathsSign in to track your progress and mark lessons complete.
Questions? Discuss in the community or start a thread below.
Join DiscordSign in to start or join a thread.