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 Service: one address that stays while pods come and go

What happens when a visitor opens your app on Kubernetes

How a Kubernetes Service address leads to one of your pods

You send a request to a Kubernetes Service, and it reaches one of your pods. Yet no machine in the cluster has the address of the Service. So where does the request change its way?

  1. 1 Shrink to the size of a request, inside node-4. The order app has just written one to the Service and lets it go.node-4order appTo: 10.96.0.20you

    Shrink to the size of a request, inside node-4. The order app has just written one to the Service and lets it go.

  2. 2 Read the envelope: it goes to the Service's address. Your 3 pods each have an address of their own, and this one is none of them. Sent like that, the request would reach nobody.To: 10.96.0.20?your 3 pods10.244.1.510.244.2.510.244.3.5

    Read the envelope: it goes to the Service's address. Your 3 pods each have an address of their own, and this one is none of them. Sent like that, the request would reach nobody.

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 kube-proxy: who keeps the rules of each Kubernetes node up to date

Share this comic

More comics