What happens when you run kubectl apply
Kubernetes controllers: how a Deployment becomes running pods
A Kubernetes Deployment is only a record. It asks for pods, but it starts none. Something has to see the difference between the record and the cluster, and fix it. Nobody sits at the keyboard to do it.
-
1
Your record asks for 3 pods, and on the nodes there are none. Between what you want and what is true, there is a gap, and a record cannot close it by itself.
-
2
And the API server starts nothing on its own: it only answers the programs that come to its door. The gap stays open until someone notices it.
The rest of this episode is for subscribers
Subscribe to read every premium episode. You can cancel when you want.
Paid yearly: $99 instead of $119.88