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

What happens when a visitor opens your app on Kubernetes

NodePort: how a request from outside gets into a Kubernetes node

A request from the internet can reach a Kubernetes node. But the app it wants runs in a pod, and the pod has an address that the internet cannot use. How does the request get from the node to the pod?

  1. 1 The proxy of your Gateway waits in its pod on node-3. node-3 has an address of its own, on the network that joins your computers, not on the internet. A request sent there reaches node-3 itself, but the proxy is one wall further in, inside its pod.node-3the Gateway's podproxySend therequests into me!To: node-3a request

    The proxy of your Gateway waits in its pod on node-3. node-3 has an address of its own, on the network that joins your computers, not on the internet. A request sent there reaches node-3 itself, but the proxy is one wall further in, inside its pod.

  2. 2 And node-3 runs several pods: the Gateway's, and two of yours. The envelope says node-3 and nothing more. So how does the request get through the wall, and find the proxy?node-3the Gateway's podproxyyour pods?To: node-3

    And node-3 runs several pods: the Gateway's, and two of yours. The envelope says node-3 and nothing more. So how does the request get through the wall, and find the proxy?

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 load balancer: the one public address your visitors use

Share this comic

More comics