Menu

One Gateway, Multiple Applications: Building Kubernetes Ingress with MetalLB and Envoy Gateway
📰

One Gateway, Multiple Applications: Building Kubernetes Ingress with MetalLB and Envoy Gateway

DEV Community: kubernetes·Abraham Naiborhu·13 days ago
#GNYBznvY
Reading 0:00
15s threshold

Hi! In the previous Kubernetes article, I discussed why seeing every node in Ready was only the first milestone. The cluster was running, but that did not mean it was ready to serve applications the way I wanted.

At that point, I could deploy a frontend and backend, give them ClusterIP Services, and communicate with them from inside the cluster.

That worked, but it only solved communication inside the cluster. It got me thinking:

How do I expose multiple applications without giving every application its own public endpoint or maintaining a collection of NodePorts?

I was building a small, non-production Kubernetes platform on existing hardware. I didn't want a new ingress design every time I added an application.

For this implementation, I chose MetalLB in Layer 2 mode, Envoy Gateway, Gateway API, and eventually Cloudflare Tunnel for external access .

But those components solve different problems. Installing all of them does not automatically produce a working request path.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.