What happens after kubectl apply
WHAT IT TESTS: the request-to-running flow across components. OUTLINE: apiserver validates and persists to etcd, scheduler binds the Pod to a Node, kubelet pulls the image and starts the container via the runtime, status flows back.
WHAT IT TESTS: whether you understand the declarative, watch-driven flow and which component does what. ANSWER OUTLINE: kubectl sends the manifest to the kube-apiserver, which authenticates, validates, and writes the Pod object to etcd. The scheduler watches for unscheduled Pods and binds this one to a suitable Node. That Node's kubelet sees the assignment, instructs the container runtime to pull the image and start the container, and reports status back through the apiserver.
Read the original → interview
- #kubernetes
- #scheduling
- #control-plane
- #pod-lifecycle
- #kubelet
Get five bites like this every day.
Tezvyn delivers a daily feed of 60-second tech bites with quizzes to lock in what you learn.