Reinventing Networking: A Deep Dive into Istio's Multicluster Gateways
summary
Istio connects clusters using Envoy proxies as gateways, CoreDNS stubs mapping remote services to node-local IPs, and Citadel-issued certificates with pass-through mTLS on port 15443 for inter-cluster security. The demo runs the Hipster Shop’s 11 microservices across three clouds (AWS, Azure, GKE) plus bare metal and completes orders end-to-end. Current setup requires one ServiceEntry per remote service and kubeconfigs for Pilot; automation is planned via MCP, Envoy filters and a synthesis registry, scalability not yet measured.
AI-written summary · about
chapters (12)
- 0:00Intro
- 0:16What is an Istio Service Mesh?
- 2:39Evolution of Traditional Networking
- 4:43Reinventing Networking with Istio
- 7:23Istio Architecture
- 9:32Service Discovery
- 12:01Connecting Gateways
- 16:20Hipster Shop Anatomy
- 16:53Hipster Shop Demo
- 21:26Automation with MCP
- 25:27Potential User Interface
- 26:18Answer Time
related talks
37mStretching the Mesh
28mMulti-Cluster Service Mesh With Istio
27mIstio's Multicluster Networking Modes: Connecting Clusters Beyond Borders
39mStitching a Service Mesh Across Hundreds of Discrete Networks
28mIstio in Action: Taking Kubernetes Traffic Control to the Next Level
30mLife Outside the Cluster: Adding Virtual Machines to an Envoy Service Mesh
37mUsing Istio to Manage the Cross-Regional & Cross-Cluster...
21mAnother Choice for Istio Multi-Cluster & Multi-Network Deployment Model