Panel: Ask Me Anything About Istio Service Mesh
summary
Istio ambient reaches alpha in Istio 1.18 and the community targets beta by fixing reliability and integrations rather than rushing GA, claiming sidecar-less operation cuts operational complexity and infrastructure cost — one customer reports 30% of costs tied to sidecars. Design splits a Waypoint proxy for destination-focused routing and a z tunnel for networking, Waypoints scale as replicas behind a service so failure is handled, Envoy stays for layer 7, and eBPF alone does not solve all mesh problems.
AI-written summary · about
chapters (9)
- 0:00Istio service mesh panel intro
- 2:50Sidecar-based mesh choice
- 6:21Multicluster Istio challenges
- 11:57Ambient mesh to Beta
- 15:50Cilium and eBPF integration
- 21:07Security and protocol support
- 26:25Cluster upgrades with Istio
- 29:16Protocol and routing
- 31:47Closing remarks
related talks
44mA Guided Tour of ISTIO Ambient Mesh
27mIstio Ambient Mesh in Production: Our Journey from Sidecar to Sidecar-less
34mAsk Me Anything
45mService Mesh War Stories - Lessons Learned the Hard Way
24mNavigating the Maze of Multi-Cluster Istio: Lessons Learned at Scale
43mProgressive Application Delivery: Istio Ambient Mesh and Argo Rollout in Action
20mHow to Optimise your Mesh with Istio Sidecar
26mChoosing a Service Mesh
