Load Balancing and Traffic Management in OCP Multi-Cluster Environments
summary
Describes migrating an OpenShift 3.11 estate to multi‑cluster OpenShift 4.8 and solving ingress and east‑west routing by combining a DNS/GTM global load‑balancer layer with a cluster mesh. Uses the Global Load Balancer Operator for DNS intelligence, an existing F5 plus its Container Ingress Service operator for north‑south traffic, and implements Silium Cluster Mesh with GlobalService=true annotations for east‑west (choosing tunneling or direct routing, encrypted control plane, and minimal manifest changes).
AI-written summary · about
chapters (16)
- 0:00Introduction
- 3:48North-South vs East-West traffic
- 5:58Multi-cluster migration
- 8:46Traffic balancing needs
- 9:10North-South with Global LB
- 13:04North-South open source
- 15:52North-South limits and East-West need
- 17:14East-West with Cluster Mesh
- 22:15Cilium Cluster Mesh implementation
- 27:18Cluster Mesh config
- 28:00Combined traffic management
- 29:25Q&A
- 31:54Q&A geo-distributed
- 34:19Independent cluster tools
- 35:47Cilium with OpenShift CNI
- 39:43Conclusion
related talks
37mBuilding the Multi-Cluster L7 Load Balancer
27mExtending Kubernetes - Lessons Learned From an L4 Ingress Implementation
22mCloud Native Multi Cluster/Multicloud Global Load Balancer for Kubernetes
32mCloud Native Global Load Balancer for Kubernetes
14mEnabling Multi-Cluster Load Balancing with Gateway API and Envoy Gateway
05mProject Lightning Talk: What's New in k8gb: CNCF's Multicluster Global Balancer
23mBuilding Unified Global Load Balancing for the Edge With k8gb
30mOptimizing costs across several OpenShift clusters