In one of my recent blog posts, I described several ways to access Kubernetes pods. One can access a pod through its IP, but pods are naturally transient. The nominal way is to configure a Service: its IP is stable, and Kubernetes’ job is to keep the mapping between a Service and its underlying pods up-to-date. Different kinds of services are available: internal only, NodePort to finally allow access from outside the cluster, and LoadBalancer that relies on a third-party component – in general, a cloud provider one. Finally, I mentioned the Ingress object, which also allows routing.
I deliberately left out the new kid on the block, the Gateway API. It’s the subject of this post.