Building the Multi-Cluster L7 Load Balancer
summary
A programmatically controlled L7 load balancer runs across 14 Kubernetes clusters in 5 regions and uses Istio/Envoy proxy for L7 routing, circuit breaking and rate limiting. The system detects IDC failures via a Dynamic DNS + healthcheck mesh (hidden primary/secondary DNS, notifications every 10s) and uses GSLB with region-specific CNAMEs for client locality. Declarative APIs, a declarative APIs and reconciliation loop with producer/consumer patterns handle async Kubernetes state, and migration APIs plus a sync command make schema and operation changes safe.
AI-written summary · about
chapters (11)
- 0:00Intro
- 2:45Catastrophic Disaster
- 5:10L7 Load Balancer
- 5:47IDC-level Failover
- 6:28Layer 7 Features
- 8:39ELB Architecture
- 10:44Address Challenges - IDC Failover
- 14:30Address Challenges - L7 Features
- 18:31Address Challenges - Programmability
- 24:14Address Challenges - Globally Available
- 28:52Address Challenges - Data Migration
related talks
22mCloud Native Multi Cluster/Multicloud Global Load Balancer for Kubernetes
27mExtending Kubernetes - Lessons Learned From an L4 Ingress Implementation
23mDemystifying Load Balancing in Istio
35mIntelligent Load Balancing in Kubernetes
23mBuilding Unified Global Load Balancing for the Edge With k8gb
32mCloud Native Global Load Balancer for Kubernetes
41mLoad Balancing and Traffic Management in OCP Multi-Cluster Environments
33mCloud Native Load Balancing From Scratch
