Menu

Why Does kubectl Say "created" When Nothing Is Running?
πŸ“°

Why Does kubectl Say "created" When Nothing Is Running?

DEV Community: kubernetesΒ·Noah GrinsteinΒ·1 day ago
#8tXNz3O6
#devtokubernetes#devto#dev#kubectl#ready
Reading 0:00
15s threshold

You run kubectl apply -f deployment.yaml . Half a second later: deployment.apps/web created . Nothing you deployed exists yet. No ReplicaSet, no Pod, no container, no IP.

"Created" means one thing: a record was written to etcd. Everything after that happens across 11 components, and most of them never talk to each other directly. They all watch the API server and react to what the previous one wrote.

kubectl ──► API server ──► etcd "created" is printed here β”‚ watches β—„β”€β”€β”€β”€β”˜ the controllers below only talk through the API server β”‚ Deployment controller ──► ReplicaSet ReplicaSet controller ──► 3 Pods (Pending, no node) scheduler ──► Pod gets a nodeName kubelet (on the node) ──► container runtime ──► CNI plugin (IP) (these three call each other directly) init containers, then app containers readiness probe ──► Pod is Ready EndpointSlice ctrl ──► endpoint flips to ready kube-proxy ──► every node can route to it first request lands here

Enter fullscreen mode

Exit fullscreen mode

kubectl to etcd (steps 1 to…

Continue reading β€” create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.