Progressive Delivery Made Easy with Argo Rollouts
summary
Adobe deploys progressive delivery with Argo Rollouts and Prometheus-driven analysis to protect 17,000 environments and over 100,000 Deployment objects, claiming automated canary promotion and automatic rollback on high error rates. Implementation uses workloadRef to adopt existing Deployments, labels for canary/stable metric separation, and a Prometheus query request_error_ratio_5m to abort bad releases. Migration pain points include orchestration for scaling down original Deployments, immutable ConfigMap/Secret rename causing rollbacks to fail, and Prometheus latency; a demo shows Argo detecting errors and rolling back successfully.
AI-written summary · about
chapters (12)
- 0:00Progressive delivery intro
- 3:12Adobe Experience Manager scale
- 5:39Why Argo Rollouts
- 7:27Canary deployments setup
- 9:53Automated rollback benefits
- 10:38Migration challenges
- 12:26Prometheus object lessons
- 14:55Low-traffic metrics handling
- 16:01Live demo Argo Rollouts
- 19:31Analysis run details
- 20:42Summary key takeaways
- 21:03Q&A
related talks
25mPrometheus Data analysis and Event Notifications for Progressive Delivery
23mStop Deploying Blind! Using Observability and Argo Rollouts to Light the Way
22mReal Time Argo Rollouts Analytics Powered by Notification Engine
23mArgo at Scale: Navigating Complex Multi-Dimensional Deployments Across H...
22mAnalysis in Action: Real-World Metrics Driven Argo Roll...
25mObservability In ArgoCD/Rollouts Using Streaming ML For Reducing MTTR
28mPanel: From Signals To Safety Nets: Self-Healing Progressive...
10mLightning Talk: Open Source Canary Deployments with Application Metric Analysis
