Multi-cluster Service Mesh Workshop
summary
Hands-on workshop builds a 3-cluster Kind lab: a Gloo Mesh management plane and two Istio data-plane clusters, deploys the Bookinfo app, and proves 3-cluster Kind setup works end-to-end. Management plane issues a shared CA and federates identity so clusters get management-plane-issued mTLS certificates. Uses meshctl, helm and istioctl, adds access-log plugin and UI, configures traffic policies including a 75% traffic shift, and demonstrates cross-cluster failover via outlier detection and observability.
AI-written summary · about
chapters (24)
- 0:00Start
- 0:28Who Am I
- 1:14Istio Architecture
- 2:24Things That You'Ll Get with Glue Mesh Enterprise
- 4:02Common Problems
- 6:15Multi-Cluster Traffic
- 20:31Deploy Istio
- 22:11Envoy Metric Service
- 22:49Cluster Two Yaml
- 28:03Virtual Mesh
- 29:59Virtual Mesh Resource
- 35:55Access Control
- 37:52Access Policies
- 45:10Traffic Policy
- 47:46Traffic Failover
- 48:44Virtual Destination
- 53:48Observability
- 54:22Access Log Record
- 55:30Install the Access Log Plug-In into Meshctl
- 57:35Glue Mesh Enterprise Ui
- 1:01:30Glue Mesh Gateway
- 1:02:30Create a Virtual Gateway
- 1:03:44Route Table
- 1:04:53Virtual Gateway
related talks
50mMulti-Cluster Kubernetes and Service Mesh Patterns
01h 33mTutorial: Istio Service Mesh Get Started Workshop
32mMulti Cluster and Multi Mesh Patterns
05mBest Practices on Setting up Multi Cluster Service Mesh in AWS
11mLightning Talk: Multi-cluster Istio Mesh – Complex or Piece of Cake?
37mBuilding a Multi-Cloud Service Mesh from the Ground Up with Kilo
58mUsing Service Meshes and Kubernetes to Solve Service-to-Service Communications...
41mService Mesh beyond single clusters