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

What happens when a visitor opens your app on Kubernetes

Kubernetes DNS: how a pod finds a Service by its name

Inside Kubernetes, one app finds another by the name of its Service, never by a number. Who turns that name into an address? And how does it learn about new Services?

  1. 1 The order app's note holds the Service's address, a number Kubernetes picked. Beside it is cafe-menu, the name you chose. So you set the order app to keep the name and drop the number.youKeep the name.Drop the number.cafe-menu10.96.0.20the order app's note

    The order app's note holds the Service's address, a number Kubernetes picked. Beside it is cafe-menu, the name you chose. So you set the order app to keep the name and drop the number.

  2. 2 But a request travels to an address, never to a name. So the order app first has to ask: what is the address of cafe-menu?order appcafe-menu,but where?To: cafe-menu

    But a request travels to an address, never to a name. So the order app first has to ask: what is the address of cafe-menu?

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 Gateway API vs Ingress: how a request from outside finds the right app

Share this comic

More comics