Kubernetes overview
The project’s own explanation of its purpose, capabilities, historical context, and boundaries.
Kubernetes · Learning path
How does Kubernetes work?
A reading path from the reason Kubernetes exists to its control-plane components and the exact sequence triggered by an API request.
Engineers who use Kubernetes and want to explain its reconciliation model and request lifecycle without hiding behind kubectl.
- 3
- stages
- 3
- selected readings
- 01
Stage 1
Know why Kubernetes exists
Explain which problems Kubernetes solves, what it deliberately leaves to other systems, and when its operational cost is justified.
- 02
Stage 2
Map the control plane and nodes
Identify which component stores state, exposes the API, schedules Pods, reconciles desired state, and runs workloads.
Kubernetes components
Maps the API server, etcd, scheduler, controller manager, kubelet, kube-proxy, and container runtime onto a cluster.
- 03
Stage 3
Trace a request through the cluster
Follow client validation, authentication, authorization, admission, persistence, reconciliation, scheduling, networking, and container startup.
What happens when Kubernetes edition
A source-linked execution trace from a kubectl command to a running Pod, including the control plane and node-side work.