Ambient Operations: Automating Istio Orchestration with Argo
summary
Ambient Mode removes sidecars so Istio upgrades become fully declarative and automatable with Argo; a live reference architecture and three demos show platform engineers spinning up patched control planes (e.g. 1.18.5 and 1.19.3), switching tags to point to new revisions, and progressively rolling a cluster to a beta 1.20 while monitoring with Locust. The system performs controlled rollouts, supports immediate rollbacks, and succeeds in the live demos with minor transient traffic blips.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 4:17Breaking the internet with pflags
- 6:00GitOps fundamentals
- 9:34Platform engineering and service mesh
- 11:40Ambient mesh objectives
- 13:27Sidecar mode upgrade challenges
- 16:37Ambient mode architecture
- 17:38Tags revisions and control planes
- 19:03Demo 1 HTTP rapid reset upgrade
- 22:15Platform engineer empowerment in security
- 22:38Upgrade planning channels and phases
- 24:02Demo 2 appdev rapid channel
- 26:11Demo 3 minor version upgrade
- 28:42Rolling back production failures
- 29:02Conclusion and Q&A
related talks
43mProgressive Application Delivery: Istio Ambient Mesh and Argo Rollout in Action
09m⚡ Lightning Talk: Operate Sidecar and Sidecar-Less Applications with Istio and ArgoCD Rollouts
28mProgressive Delivery With Argo Rollouts and Kubernetes Gateway API for Multi-Directional...
46mProgressive Delivery in the Kubernetes era
35mProgressive Delivery with Argo Rollouts
30mProgressive Delivery Made Easy With Argo Rollouts
27mUps, let's revert! 🔥 Automating Kubernetes Rollouts with Argo a...
23mStop Deploying Blind! Using Observability and Argo Rollouts to Light the Way