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 Kubernetes controllers: how a Deployment becomes running pods

What happens when you run kubectl apply

The Kubernetes scheduler: how a pod gets its node

A Kubernetes cluster has many nodes. Some are busy, and some are nearly empty. Every new pod goes to exactly one node. If you had to choose the node, how would you choose?

  1. 1 None of your 3 pods has a node yet. Such a pod is Pending: accepted by the cluster, and not running yet.Pendingpodno nodepodno nodepodno nodenode-1node-2node-3node-4

    None of your 3 pods has a node yet. Such a pod is Pending: accepted by the cluster, and not running yet.

  2. 2 One program of the control plane picks a node for each pod that has none: the scheduler. It takes your pods one at a time.schedulerA pod with no node?That's my job.pod

    One program of the control plane picks a node for each pod that has none: the scheduler. It takes your pods one at a time.

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 kubelet: how a Kubernetes node finds its pods

Share this comic

More comics