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 How a Kubernetes Service address leads to one of your pods

What happens when a visitor opens your app on Kubernetes

kube-proxy: who keeps the rules of each Kubernetes node up to date

A Kubernetes node stops in the night, and its pods stop with it. In the morning, no other node sends requests to those pods any more. Nobody changed a rule by hand. So who changed the rules on every node?

  1. 1 One Sunday, while you sleep, node-2 stops with your pod on it. Every node still keeps the rule it had.Sundayyour clusternode-1node-2node-3node-4stopped

    One Sunday, while you sleep, node-2 stops with your pod on it. Every node still keeps the rule it had.

  2. 2 On node-4, the rule still names the pod that is gone. A request sent down that line gets no answer.node-4order apprulefor 10.96.0.20:10.244.1.510.244.2.510.244.3.5To:10.96.0.2010.244.2.5no answernode-2, stopped

    On node-4, the rule still names the pod that is gone. A request sent down that line gets no answer.

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 DNS: how a pod finds a Service by its name

Share this comic

More comics