Tailored Deployment Strategies: Argo Rollouts for Diverse Applications
summary
Adobe Experience Platform adopts Argo CD, Argo Workflows, Argo Events and Argo Rollouts to add progressive deployments that reduce blast radius and integrate existing functional tests. REST API uses preview replica count = 1 with a pre-promotion analysis job (reuse existing tests) and HPA-managed active pods; the Kafka consumer uses a canary with error rate < 1% and a production-metrics check scraped every ~15s, using Prometheus pod-label scraping via rollout metadata to isolate canary pods; typical canary runtime is 5–10 minute and rollbacks are reflected back to git.
AI-written summary · about
chapters (7)
- 0:00Argo Rollouts intro
- 3:15Progressive deployment motivation
- 5:20Blue-green for RESTful web service
- 8:28Kafka consumer blue-green challenges
- 10:12Canary with Kafka metrics
- 14:09Key takeaways from streaming
- 16:18Rollbacks and GitOps
related talks
06m⚡ Lightning Talk: Improving Release Reliability with Argo Rollouts Across 10k Customer Services
29mTuning Argo Rollouts for Thousands of Workloads
24mArgo Rollouts from the Trenches – Next Level Progressive Delivery Best Practices
30mProgressive Delivery Made Easy With Argo Rollouts
35mProgressive Delivery with Argo Rollouts
23mStop Deploying Blind! Using Observability and Argo Rollouts to Light the Way
46mFrom FTP to ArgoCD & Argo Rollouts: An adoption history inside a corp
28mCross-Cluster Progressive Delivery: Rolling Out Apps With Arg...