Using Istio to Manage the Cross-Regional & Cross-Cluster...
summary
Shows a concrete deployment: a multi-cluster Istio mesh across Alibaba Cloud regions that maps Kubernetes services by DNS, uses Istio/East‑West routing and Envoy sidecars to route traffic, and implements passive cross-region failover so requests to a downed region redirect to healthy clusters. Describes topology choices, how service-to-service mTLS and traffic policies are applied, and a live demo where API requests fail over from one region to another and continue serving without manual intervention.
AI-written summary · about
chapters (10)
- 0:00Start
- 1:01Why need the multiple regions/clusters? 1. Business Continue/Disaster Recovery 2. Geographically distributed end users
- 9:30Feature Request for multi-region/cluster
- 11:39Istio multi-cluster patterns
- 13:50Simplified Installation and Configuration (2) S
- 14:06Custom Resource for Istio Operator
- 18:17How to enable locality aware & failover?
- 20:13Customer Case Reference - Unicareer
- 29:47Quick Demo
- 35:47Benefits from Istio on ACK
related talks
45mIstio Service Mesh Simplified Beyond a Single Cluster
24mMulticluster Service Mesh
31mMulti(Control Plane/Network/Mesh)??: A Practical MultiCluster...
40mIstio, your K8S cluster best friend
58mUsing Service Meshes and Kubernetes to Solve Service-to-Service Communications...
50mDeveloping Microservices with Istio
52mEmpower Your Microservices with Istio Service Mesh
58mService Mesh and Sidecars with Istio and Envoy
