Istio Multi-Cluster Mesh Expansion BOF
summary
Demo shows a working Istio multi‑cluster mesh where Envoy sidecars in remotes talk to a central Pilot that knows all services, deployed with Helm charts for install and using per‑cluster Citadel instances chained to a common root for mTLS. Alternatives discussed are federated pilots exchanging endpoints or running a single pilot HA across clusters (run in multiple clusters). Mixer scaling options include per‑cluster or per‑node instances; outstanding issues are global quotas, gateway tunneling/zeroVPN for networking, and integration with the Kubernetes cluster registry.
AI-written summary · about
chapters (14)
- 0:00Intro
- 3:35Single Control Plane
- 5:40Pilot Models
- 8:20Why even do Federation
- 10:30Models
- 17:10Identity
- 19:10Networking
- 23:10MultiCluster Mesh Expansion
- 26:30Cluster Registry
- 28:30MultiCluster Applications
- 30:50MultiCluster Models
- 32:30Tradeoffs
- 33:55Scaling
- 36:35Naming
related talks
08mIstio Adoption Journeys
36mKubernetes Multi-Cluster Made Easy - Federica Ciuffo and Marco Ballerini
06mLightning Talk: Optimizing Multi-Cluster Communication and Cost Efficiency with A...
22mDon't Ship the Org Chart: Rebuilding Istio for User Maintainability
31mThe Truth About the Service Mesh Data Plane
44mStretching the Service Mesh Beyond the Clouds
01h 02mIntro + Deep Dive: Multicluster SIG
13mWhich Edge Are You on? Service Affinity with Cilium Cluster Mesh