From FTP to ArgoCD & Argo Rollouts: An adoption history inside a corp
summary
Company migrates from Azure App Services and Azure Pipelines to Kubernetes with ArgoCD and Argo Rollouts, moving from portal boxes to GitOps and centralized Argo control plane while keeping developer workflows. Migration supports multi-cluster/multi-region via ApplicationSets and cluster generators, replaces many pipelines with repo-driven sync, and runs per-cluster Argo Rollouts CRDs to perform last‑mile smoke tests (k6 jobs) before canary shifts. Results: critical mission software for 90 million active users cuts disaster recovery from 68 hours to 30 minutes.
AI-written summary · about
chapters (14)
- 0:00Deployment evolution intro
- 3:01FTP to code repositories
- 7:55Pipelines and infrastructure as code
- 11:09Kubernetes for scalability
- 14:16Planning Kubernetes adoption
- 16:03Why GitOps with Argo CD
- 21:06Developer experience with Argo CD
- 24:20Multi-cluster deployments simplified
- 28:40Teams transitioning to GitOps
- 31:33Kubernetes rollout limits
- 33:20Argo Rollouts for smart deployments
- 36:27Argo Rollouts demo
- 43:23Security and rollback in production
- 44:07Q&A
related talks
27mArgoCD as the Engine of a Brownfield Migration to Kubernetes
18mTailored Deployment Strategies: Argo Rollouts for Diverse Applications
25mSailing Across the Ocean of Argo Ecosystem Like a Pro
24mArgo Rollouts from the Trenches – Next Level Progressive Delivery Best Practices
04mA Holistic Approach to Software Delivery with Argo
25mHow to Multiply the Power of Argo Projects By Using Them Together
27mExploring Argo
32mIntroduction to ArgoCD