Most of us run kubectl apply -f dozens of times a day without thinking about the machinery it sets in motion. But when something breaks, a Pod stuck in Pending, a Service that won't route, a Deployment that never converges, understanding that machinery is the difference between guessing and debugging.
In this article, I'll map the end-to-end flow onto the actual Kubernetes architecture, so you can see not just what happens, but which component is responsible at every step.
The Architecture at a Glance
Kubernetes is split into two planes:
Control plane: the brain. It makes decisions: what should exist, where it should run, and whether reality matches intent.
