You are signed in. Close

You are signed out. Close

Thank you. Your subscription has started. Close

Thank you. You will get an email when a new comic comes out. Close

We could not confirm your payment. If you paid, use the link "Sign in" at the bottom of the page. Close

Something went wrong on our side. Please try again in a moment. Close

Previous episode The Kubernetes scheduler: how a pod gets its node

What happens when you run kubectl apply

The kubelet: how a Kubernetes node finds its pods

The Kubernetes control plane picks a node for every pod. Then it does not tell that node. Yet a moment later, the pod starts on that node.

  1. 1 The scheduler wrote node-1 on a pod, at the control plane. node-1 itself is a computer of its own, a little further off.control planeAPI serverpod fornode-1A pod fornode-1.node-1

    The scheduler wrote node-1 on a pod, at the control plane. node-1 itself is a computer of its own, a little further off.

  2. 2 No program of the control plane goes out to deliver the pod.So who tellsnode-1 it haswork to do?

    No program of the control plane goes out to deliver the pod.

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

Next episode The container runtime: who really starts your container in Kubernetes

Share this comic

More comics