Is Zero-Downtime Migration Possible? Moving From Ingress & Sidecars To Gateway API
Talkat Istio Day North America 2025 · on Monday, 2025-11-10· at 16:35· Building B | Level 4 | B406b-407·
summary
Harri migrates production from AWS App Mesh (Envoy sidecars) to Istio Ambient and Gateway API in-place on the same EKS cluster, finishing by Feb 2025 after starting Kubernetes in June 2021; backend serves ~19 million employees across 750 clients and 8,000 locations. The team uses Gateway API + NLB to replace API Gateway (30s integration limit), deploys waypoint for L7 and JWT validation integrated with Cognito/JWKS, relaxes mTLS during cutover, and reports 40% fewer containers and a zero-downtime migration in-place with Gateway API + waypoint as the final topology.
AI-written summary · about
chapters (9)
- 0:00Introduction and context
- 1:34Service mesh journey
- 3:40Selection criteria
- 5:05Evaluating mesh options
- 10:18Advantages of ambient mode
- 11:59Istio ambient demonstration
- 15:43Migration execution story
- 20:23Migration considerations
- 26:03Operational challenges and wrap-up
related talks
24mI Tested 7 So You Only Need 1: Your First Gateway API Migration in 5 Minutes
19mZero-Downtime by Design: High-Availability Migration Patterns
40mThe Busy Platform Engineers Guide to API Gateways
24mLeveraging Gateway API for Kubernetes Native API Management
47mGatewayAPI, 10 Years of Maturation for a New Kubernetes API
28mMaking the Leap: What Gateway API Needs To Support Ingress-NGINX Users
19mPlanning the Zero-Downtime Lifecycle of Your Service Mesh
26mSynchronous Communication Patterns: A journey from ESB to APIs [...]
