Multicluster Service Mesh
summary
Describes using Envoy sidecars and an Istio control plane across two Kubernetes clusters and shows that a central glue mesh management plane can replace dozens of per-cluster Istio configs. Demo creates one policy that routes 75% of traffic to review v3 in cluster two and 15% to v1 and 10% to v2 in cluster one, and the UI shows the expected red-star traffic from the remote cluster. Claims scale benefits for hundreds of clusters and simpler auth, routing and observability.
AI-written summary · about
chapters (15)
- 0:00Intro
- 0:25Agenda
- 1:05Microservice Architecture
- 4:22Service Mesh
- 5:54Envoy
- 7:53Istio resources
- 8:24Access control in Istio
- 8:40Spiffe in Istio
- 10:14Multi Clusters
- 10:49Shared Control Plane
- 11:17Replicated control plane
- 12:00Multi Cluster Use case
- 14:52Multi cluster concerns
- 17:58Multi Cluster Trust and Identity management
- 22:40Gloo Mesh
related talks
45mIstio Service Mesh Simplified Beyond a Single Cluster
53mService Mesh: What, Why, And How?
55mEmpower Your Microservices with Istio Service Mesh
58mUsing Service Meshes and Kubernetes to Solve Service-to-Service Communications...
58mService Mesh and Sidecars with Istio and Envoy
50mService Mesh and Sidecars with Istio and Envoy
01h 03mJust what is a "service mesh", and if I get one will it make everything OK?
31mMulti(Control Plane/Network/Mesh)??: A Practical MultiCluster...
