Using Service Mesh in Multi-Cluster Kubernetes Environment for DR Use Case
summary
Uses Istio single-mesh multi-cluster to manage traffic and an orchestrator that chooses failover sites by cost and network metrics. Demo injects a failure: on‑prem link shows 20 ms → 60 ms latency, RPS drops to zero and automated failover completes in about 2 minutes. Service colocation after orchestration brings end‑to‑end latency from ~6 seconds down to ~240–443 ms. Implementation is fully automated and successfully migrates traffic across clusters and regions.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 2:16Service Mesh
- 2:51Service Mesh Deployment Model
- 3:09Infrastructure Impact
- 4:37Use Case Example
- 5:53Demo
- 8:54Summary
related talks
50mMulti-Cluster Kubernetes and Service Mesh Patterns
58mUsing Service Meshes and Kubernetes to Solve Service-to-Service Communications...
41mService Mesh beyond single clusters
26mAn Introduction to Service Mesh in Action
11mLightning Talk: Multi-cluster Istio Mesh – Complex or Piece of Cake?
37mThe Service Mesh Wars: A New Hope for Kubernetes
12mService Mesh & Kubernetes Multicluster Communication With Linkerd
01h 31mMulti-cluster Failover Using Linkerd