From FTP To Argo CD & Argo Rollouts: An Adoption History Insid...
summary
A large retail SSO and mission software with more than 90 million users moves from Azure App Services and manual pipelines to a GitOps pipeline using Argo CD and automated canaries via Argo Rollouts, plus ApplicationSet and cluster generators to manage thousands of apps and multicluster DR. CI uses Terraform, Azure Pipelines, repo-as-source truth, and Packflow-driven end‑to‑end/contract checks that trigger roll forward or automatic rollback; recovery time drops from a week to 5-minute recovery and QA shifts to defining gate analyses.
AI-written summary · about
chapters (16)
- 0:00Deployment transformation journey
- 3:16What defines a deployment
- 5:02Manual FTP and Terraform
- 6:27QA challenges in stone age
- 7:56Pipeline bottlenecks
- 9:42Failing infra and tech shift
- 10:24Adopting Kubernetes
- 11:49GitOps with Argo CD
- 13:21Argo CD automates deployments
- 15:32Disaster recovery in five minutes
- 15:52Argo CD Application and ApplicationSet
- 16:56Argo Rollouts for canary
- 17:17Canary strategy and rollbacks
- 19:06Argo CD impact on productivity
- 19:27Live demo of Argo Rollouts
- 21:38Q&A
related talks
25mSailing Across the Ocean of Argo Ecosystem Like a Pro
43mGitOps at Scale with and Argo CD on
05mLessons from a Large-Scale GitOps Implementation
42mLet's Learn About ArgoCD
06mKeynote: Scaling Argo for the Enterprise
42mArgo Family: GitOps in first class
30mArgo’s Vibrant Ecosystem and Community
23mArgo at Scale: Navigating Complex Multi-Dimensional Deployments Across H...