Enabling Multi-Cluster Load Balancing with Gateway API and Envoy Gateway
summary
Demo of a production pattern: a dedicated LB cluster runs Envoy Gateway plus a centralized control plane and syncs tenant clusters via a pair of controllers, QLB manager and QLB agent, which copy Services into the LB cluster, create Gateway API CRs and expose backends over an XDS-configured Envoy using a bridge Service and EndpointSlice-backed single IP:port per backend. Trade-offs: one more cluster to operate and scale, but easier multi-cloud/on‑prem consistency, cert/DNS centralization, and per-tenant isolation.
AI-written summary · about
chapters (7)
- 0:00Introduction to networking
- 1:24Load balancing challenges
- 2:39Gateway API and Envoy
- 4:41Introduction to KubeLB
- 6:46KubeLB architecture and flow
- 10:33Trade-offs and benefits
- 12:49Conclusion and Q&A
related talks
14mMulti-cluster, Blue-green Traffic Splitting with the Gateway API
31mBehind the Scenes of Building a Gateway API Dataplane...
29mgRPC load balancing and Service Mesh
23mDemystifying Load Balancing in Istio
33mCloud Native Load Balancing From Scratch
37mBuilding the Multi-Cluster L7 Load Balancer
42mSIG Multi-Cluster Deep Dive
16mKeynote: LLM-Aware Load Balancing in Kubernetes: A New Era of Efficiency