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 container runtime: who really starts your container in Kubernetes

What happens when you run kubectl apply

The Kubernetes control loop: why your app keeps running when a node stops

A Kubernetes node stops, and your pods on it stop too. A few minutes later, the pods run again on other nodes. Nobody typed a single command.

  1. 1 Sunday again, and node-2 stops, its container with it. You are fast asleep.Sundaynode-1node-2node-3node-4stopped

    Sunday again, and node-2 stops, its container with it. You are fast asleep.

  2. 2 Each kubelet tells the API server, every few seconds, that its node is alive. node-2 goes silent, and a controller notices.API servercontrollernode-2? Nota word.node-1Stillhere!node-2node-3Stillhere!

    Each kubelet tells the API server, every few seconds, that its node is alive. node-2 goes silent, and a controller notices.

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

You finished the comic Back to the comic

Share this comic

More comics