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 API server: the one door of the control plane

What happens when you run kubectl apply

etcd: where Kubernetes writes down your wish

You tell Kubernetes what to run. It must remember this for months, even when its parts restart or fail. The whole cluster keeps its memory in one small database. Writing to that database starts nothing.

  1. 1 For now, your Deployment is still in the hands of the API server, and that is a weak spot. The API server is a door: it checks what comes in, and keeps no records of its own.API serveryourDeploymentI check.I don't keep.

    For now, your Deployment is still in the hands of the API server, and that is a weak spot. The API server is a door: it checks what comes in, and keeps no records of its own.

  2. 2 And tonight it may restart, after an update for example. If your wish lived only in its hands, the API server would come back tomorrow with nothing, and nobody would ever start your 3 pods.tonightrestartsyourDeploymenttomorrowAPI serverYour Deployment?What Deployment?

    And tonight it may restart, after an update for example. If your wish lived only in its hands, the API server would come back tomorrow with nothing, and nobody would ever start your 3 pods.

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

Share this comic

More comics