Multi-Cluster Service Mesh With Istio
summary
Shows how Istio implements multi-cluster service discovery and routing using Kubernetes plus Istio features: DNS proxy introduced in Istio 1.8, the istio-coredns plugin to populate cluster name tables, and east-west gateway plus EDS for cross-network endpoints. Describes concrete patterns — single-network primary remote, single-network multi-primary, and multi-network with per-cluster control planes — and reports practical limits: no session stickiness via gateways, headless services failing across clusters, and the need for mTLS and network-aware locality to avoid unnecessary cross-cluster traffic.
AI-written summary · about
chapters (14)
- 0:00Start
- 0:49Agenda
- 1:38Why do we need multi-cluster?
- 4:37Challenges for multi-cluster
- 6:50What is Istio?
- 9:09Multi-cluster Service Mesh
- 11:15DNS Resolve-Before v1.8
- 13:30DNS Resolve- After v1.8
- 18:03Different networks gateway
- 19:10Single network: Primary-Remote Services con
- 20:34Single network: Multi-Primary
- 20:59Different networks: Multi-Primary Services con
- 22:05Different network: Gateway
- 23:34What can be improved?
related talks
37mReinventing Networking: A Deep Dive into Istio's Multicluster Gateways
36mCross-Cluster Calls Made Easy with Istio 1.1
27mIstio's Multicluster Networking Modes: Connecting Clusters Beyond Borders
37mUsing Istio to Manage the Cross-Regional & Cross-Cluster...
21mAnother Choice for Istio Multi-Cluster & Multi-Network Deployment Model
37mStretching the Mesh
39mStitching a Service Mesh Across Hundreds of Discrete Networks
28mIstio in Action: Taking Kubernetes Traffic Control to the Next Level