Run kubectl apply and follow every message along the floor spokes: through the API server's stamps, into etcd, out to the controllers, the scheduler and the kubelet. Turn off auto-play to step through it, or press ▶ Guided tour.
| Kind (in etcd) | Name | State |
|---|
kubectl only talks to the API server, and so does every other component: the API server authenticates and authorizes each request, runs admission, and is the only part that reads and writes etcd. The rest happens by watching: the deployment controller creates a ReplicaSet, the replicaset controller creates pods, the scheduler binds them to nodes, and the kubelet has the container runtime start them, then reports status. Deleting a pod is repaired the same way.