Istio Multi-Cluster Service Mesh Patterns Explained
summary
Three concrete Istio multi-cluster patterns: flat-network single control plane routes pod-to-pod across clusters (requires non‑overlapping, routable pod IPs and low latency); gateway-based single control plane uses ingress/egress gateways and split‑horizon EDS so clusters can be isolated but centrally configured; multi control planes per cluster runs full Istio per cluster with service entries and global DNS for isolation and scale at the cost of managing multiple control planes and a common root CA. Demo uses IBM Cloud private clusters, edge/private node pools, NLBs, sidecar injection, and mTLS.
AI-written summary · about
chapters (9)
- 0:00Intro
- 1:00Multicluster and Multicloud
- 3:01Customer Requirements
- 4:56Cluster configuration
- 6:42Private Cluster Access
- 11:19Istio Architecture
- 15:07Single network, single control plane
- 19:30Single control plane, separate networks
- 22:38Multiple control planes
related talks
32mMulti Cluster and Multi Mesh Patterns
50mMulti-Cluster Kubernetes and Service Mesh Patterns
31mReliable multi-cluster application architectures with Istio
38mBuilding Hybrid Clouds with Istio
11mLightning Talk: Multi-cluster Istio Mesh – Complex or Piece of Cake?
43mService Mesh for developers
05mBest Practices on Setting up Multi Cluster Service Mesh in AWS
36mBuilding a Multi Cluster/Env Service Mesh at Airbnb