What happens when you run kubectl apply
The container runtime: who really starts your container in Kubernetes
A new Kubernetes node holds nothing of your app: not the code, not its image. The kubelet on the node does not run containers either. So who really starts your container?
-
1
So the kubelet hands the job to another program on node-1, one made only to run containers.
-
2
To start a container, it needs the image of your app, and that image has never been on node-1.
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