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

What happens when a visitor opens your app on Kubernetes

Kubernetes Gateway API vs Ingress: how a request from outside finds the right app

One Kubernetes cluster can run many websites. Every request from the internet has to reach the right app. The older Ingress still does this job, but Kubernetes adds nothing to it any more. The new features go to the Gateway API.

  1. 1 Rono wants two sites: his menu at menu.example, and online orders at order.example, taken by his order app. Both run in your cluster.RonoThe menu, andonline orders too!menu.exampleorder.exampleyour cluster

    Rono wants two sites: his menu at menu.example, and online orders at order.example, taken by his order app. Both run in your cluster.

  2. 2 Each request from a phone carries, inside it, the name of the site the person typed. The rules of your nodes only read the address on the outside.menu.exampleTo: an addressoutside: the onlypart the rules readinside: the site

    Each request from a phone carries, inside it, the name of the site the person typed. The rules of your nodes only read the address on the outside.

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 NodePort: how a request from outside gets into a Kubernetes node

Share this comic

More comics