Cloud Native Promises, On-Premises: Bump Your Load Balancing To V2 With Cilium
summary
Etraveli replaces proprietary appliances with Cilium (eBPF + Envoy) to move load balancing to a V2 that advertises the same load‑balancer CIDR from all nodes, peers via BGP and uses LB-IPAM, BGP, Gateway API to glue control and data planes into Kubernetes across three OpenStack DCs. Architecture runs active-active ECMP with a per‑node proxy so capacity grows with each node, observability is native, migration happens in place and two migrated services hit 7–8k req/s with TLS enabled.
AI-written summary · about
chapters (12)
- 0:00Cloud-native promises
- 1:04Scalability goals
- 3:28On-premises challenges
- 5:14V1 limitations
- 6:38Cilium as V2 solution
- 7:22V2 active-active load balancing
- 8:29V2 components: IPAM, Gateway API, BGP
- 12:43V1 vs V2 comparison
- 13:46Day two operations & migration
- 15:52Future features & community
- 16:35Key takeaways
- 18:19Q&A
related talks
29mThe Swiss Army Knife of Cloud Native Networking
33mCloud Native Load Balancing From Scratch
35mNext-level Kubernetes Networking with Cilium - Nico Meisenzahl and Philip Welz
27mCilium Cluster Mesh: The eBPF-Powered Multicluster Solution for Kubernetes
33mIKEA Private Cloud, eBPF Based Networking, Load Balancing, and Observability with Cilium
05mLightning Talk: Unveiling 5 Essential Insights from Cilium Implementation in a...
33mCloud Native Load Balancing From Scratch
24mThe Cilium Story - Why We Created Cilium