Scaling a GitOps Platform at Adobe
Talkat GitOpsCon North America 2024 · on Monday, 2024-04-15· at 10:55· Level 3 | Room 320 | Track 1·
summary
Adobe scales a GitOps platform called Flex to manage ~10,000 Kubernetes services across ~350 clusters in 28 geos, using Argo CD and Argo Workflows; the largest Argo CD instance syncs ~12,000 apps and ~600,000 resources. Engineering tunes Redis and etcd, excludes CNIs and endpoints, raises timeouts and GRPC limits, reduces repo-server parallelism, archives workflows and deletes completed pods, and shards load into multiple Flex boxes with zero‑downtime relocation to avoid flapping apps and uses archive workflows to control datastore growth.
AI-written summary · about
chapters (10)
- 0:00Scaling GitOps at Adobe
- 1:22Flex GitOps platform at Adobe
- 2:45Journey phases and challenges
- 3:48Vertical scaling and tuning
- 9:25Fixing apps and workflows
- 12:35GitOps engine performance tips
- 13:37Horizontal scaling and Flex boxes
- 16:26Lessons and scaling recommendations
- 18:34When to tune for scale
- 19:41Q&A on Argo CD scaling
related talks
21mKey Takeaways from Scaling Adobe's CI/CD Solution to Support..
36mHow the @#$! Do I Deploy That Many Apps to That Many Clusters? How Adobe Scaled on GitOps
37mSecure Multi-Tenant GitOps Application & Infrastructure Rollouts At Adobe
43mGitOps at Scale with and Argo CD on
26mGitOps Me Some of That! Managing Hundreds of Clusters with Argo CD
37mPanel: Building a GitOps...
24mScaling GitOps Using ArgoCD Application-Sets: Lesson Learnt
05mLessons from a Large-Scale GitOps Implementation