Multi(Control Plane/Network/Mesh)??: A Practical MultiCluster...
summary
Enterprise customers find community multi-cluster Istio patterns fragile, so the team builds a pragmatic alternative: per-cluster Istio control planes scoped to local services, plus replicated gateways as product front doors that advertise APIs across clusters. Gateway discovery is automated, service entries use a virtual IP with endpoints for local cluster IP and remote gateway IP, and east‑west traffic uses port 15443 east‑west mTLS. Result: locality‑aware routing, reduced blast radius for upgrades, lower egress costs, and successful production deployments for finance and defense customers.
AI-written summary · about
chapters (13)
- 0:00Intro
- 2:16Resiliency
- 3:46Unintelligent Routing
- 4:40Complex Architectures
- 5:12Adopting Service Mesh
- 8:08Replicated Control Pane: Simplified
- 9:32Istio Suggested Replicated Control Plane
- 13:58Developer Mindset
- 17:06Embrace the Gateway
- 18:35Using Gateways Logically
- 22:53Practical Approach: Service Owner Pov
- 23:26Practical Approach: Configuration Flow
- 26:59Communication Flow
related talks
24mMulticluster Service Mesh
37mUsing Istio to Manage the Cross-Regional & Cross-Cluster...
40mReimagining Application Networking and Security
06mLightning Talk: Unifying Hybrid Clouds: A Journey Through Multi-Control...
27mSingle Mesh vs Multi Mesh- Tradeoffs for Enterprise Multi-Tenant Support- Ding Shaojun (Iris Ding) & Zhang Huailong (Steve Zhang), Intel
28mDebunking the Istio Is Complex Meme
11mKeynote: Multicluster Strategies to “Kubernetify” Legacy Apps
40mIstio, your K8S cluster best friend