Multicluster Ingress Powered by Kubernetes Cluster Registry - Greg Harmon & Nikhil Jindal
summary
Demo shows a controller and CLI (cube-mci) that use a Cluster Registry to program a Google Cloud Load Balancer and provide a single anycast IP to three clusters (Asia, Europe, US). Controller watches cluster objects and ingresses, automatically adds/removes backends, honors GCLB health checks, and shifts traffic by nearest-region routing; the live demo works end-to-end. API remains alpha and currently only implements least-latency mode.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:04Why run multiple clusters
- 2:07Problems with single clusters
- 3:44What is Multi clustering
- 5:17Advantages of Multi clustering
- 7:07Kubernetes Cluster Registry CLI
- 8:16Demo
- 11:35Cluster Registry
- 17:17Ingress Demo
- 25:58QA
- 27:58Advanced load balancing
- 28:36Integrations
- 29:10How does it help
- 30:27Kubernetes Cluster Registry
related talks
36mKubernetes Multi-Cluster Made Easy - Federica Ciuffo and Marco Ballerini
27mExtending Kubernetes - Lessons Learned From an L4 Ingress Implementation
37mBuilding the Multi-Cluster L7 Load Balancer
14mMulti-cluster, Blue-green Traffic Splitting with the Gateway API
30mHow to Coordinate Your Multi-cluster Kubernetes Environment with Ease
34mBuilding a Cluster Management API using Kubicorn
35mDynamic Multi-Cluster Controllers With Controller-runtime
36mThe Multicluster Toolbox