Stretching the Mesh
summary
Demonstration shows a single Istio control plane (Pilot) running in GKE that pulls service and endpoint data from multiple Kubernetes API servers, with Citadel certs chained to one root and Envoy using XDS/SDS to discover cross-cluster endpoints. Deployment uses headless services and pod IP reachability between GKE and on‑prem, a file‑based cluster registry to list clusters, and Bookinfo with reviews v1/v2 on GKE and v3 on‑prem. Route rules steer user "jason" traffic to v3 proving cross‑cloud canary routing.
AI-written summary · about
chapters (22)
- 0:00Introduction
- 0:52Agenda
- 1:28Goal
- 2:17Service Mesh
- 3:24VCO Architecture
- 4:39MultiCluster Architecture
- 6:17Pilot
- 7:21Envoy
- 9:14Deployment
- 10:38GCP
- 11:09Application Flow
- 13:00Details
- 13:47PreDeploy
- 14:23Deploy
- 18:41Endpoints
- 20:28Review Service
- 20:52After Deployment
- 21:51Request to Pilot
- 23:02Cluster
- 25:01Technical difficulties
- 27:24Sample app
- 32:20Questions
related talks
37mReinventing Networking: A Deep Dive into Istio's Multicluster Gateways
30mLife Outside the Cluster: Adding Virtual Machines to an Envoy Service Mesh
28mMulti-Cluster Service Mesh With Istio
15mSimplify Kubernetes Connectivity
31mClean-up Your Service Mess with Service Mesh
28mIstio in Action: Taking Kubernetes Traffic Control to the Next Level
44mStretching the Service Mesh Beyond the Clouds
36mKubernetes as the Universal Control Plane: From Pods to Multi-Cloud Infrastructure