How to Optimise your Mesh with Istio Sidecar
summary
Use Istio Sidecar to limit discovery to only required hosts instead of pushing full cluster config, implement per-service Sidecar resources and a rollout runbook with pairing, dashboards and checks. Deployment touches over 300 services and >30 teams, completes with no disruptions and yields >60% memory and compute reduction for Envoy sidecars, eliminates update lag so clusters converge instantly, and combines partial automation with developer collaboration for safe, auditable rollouts.
AI-written summary · about
chapters (8)
- 0:00Introduction and speaker intro
- 1:28Istio service mesh overview
- 4:46Scalability issues in service discovery
- 7:14Using Sidecar resource for optimization
- 9:03Collaborating with developers on rollouts
- 13:17Rollout results and benefits
- 15:04Steps for successful rollouts
- 18:57Key takeaways and conclusion
related talks
21mIteratively Implementing Istio: Zero to Service Mesh with No Downtime
28mService Mesh and Sidecars with Istio and Envoy
28mService Mesh: Demystifying Istio
27mIstio Ambient Mesh in Production: Our Journey from Sidecar to Sidecar-less
58mService Mesh and Sidecars with Istio and Envoy
43mService Mesh for developers
01h 01mMeshing Around with Istio
50mService Mesh and Sidecars with Istio and Envoy
