Kubernetes: APIs, control loops and execution
Prerequisites: Start here / basic technical literacy
01 / The control plane coordinates
Scroll the diagram sideways for readable labels.
Desired state is a promise to keep
Scroll the diagram sideways for readable labels.
Learning objective and mental model verified
Trace a declared workload to running containers. The API server exposes and validates the cluster API; etcd holds cluster state. Controllers reconcile objects, the scheduler places unassigned Pods, and node kubelets coordinate with the container runtime. CNI and CSI integrations supply networking and storage interfaces.
[S01]Mechanism verified
A controller observes resources, compares actual state with the desired specification and requests changes. Different controllers handle separate responsibilities. Reconciliation is repeated, rather than a one-time deployment script.
[S02]Worked example synthesis
Suppose a quote API should have three replicas and one Pod disappears. Its ReplicaSet creates another Pod. Scheduling, image retrieval, startup and readiness still need to succeed. The application must preserve durable state outside that replaceable process.
[S04] [S02]Decision, pitfall and improvement synthesis
For an illustrative service, declare the desired count through a Deployment rather than manually creating replacement Pods. Keep spare placement capacity and test recovery delay. A controller cannot repair invalid credentials, an unavailable database or insufficient subnet addresses merely by trying again. This inference follows from the separate scheduling and execution responsibilities; it is not a recovery-time guarantee.
[S01] [S02]Check yourself: Does deleting a Pod necessarily lose customer records?
Only if the records depended on that Pod’s ephemeral state. Replica replacement restores process capacity; durable data and recovery are separate concerns.