Key Takeaways from Scaling Adobe's CI/CD Solution to Support..
summary
Adobe's Flex starts in 2022, hits instability around ~1,500 Argo CD apps, and now runs ~11,000 Argo CD apps while targeting >50,000. Engineering fixes include sharding and replica increases, moving custom components to Argo CD APIs to use the informer cache, raising reconcile timeout 3→9 min, and reducing etcd churn; a new Flex in a box design adds a redirect service and horizontal Flex boxes to split load and cut a 50,000-app sync to ~24 minutes.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 0:30Agenda
- 1:04What is Flex
- 3:58Adobes Flex Journey
- 5:28Adobes Challenges
- 6:39Adobes ETD Issues
- 8:23Flex Journey
- 10:01Key Stability Improvements
- 11:41Reconciliation Timeout
- 12:56Sharding
- 14:24Flex in a Box Architecture
- 17:49Future Extensions
- 18:25VClusters
- 19:12Key takeaways
related talks
26mScaling a GitOps Platform at Adobe
36mHow Adobe Planned For Scale With Argo CD, Cluster API, And VCluster
23mArgo at Scale: Navigating Complex Multi-Dimensional Deployments Across H...
36mHow the @#$! Do I Deploy That Many Apps to That Many Clusters? How Adobe Scaled on GitOps
29mTuning Argo Rollouts for Thousands of Workloads
06m⚡ Lightning Talk: Improving Release Reliability with Argo Rollouts Across 10k Customer Services
18mTailored Deployment Strategies: Argo Rollouts for Diverse Applications
28mClick-Free Environment Promotion Driven by ApplicationSets Progre...