Major League Baseball + Argo CD: A Home Run
summary
Major League Baseball migrates to GCP and Kubernetes and runs a single Argo CD instance that manages 6200 applications (900 unique) across almost 200 clusters including a cluster in each ballpark. CI/CD uses a monorepo with app-of-apps, ApplicationSets with cluster label generators, and secret handling via SOPS + Helm Sops mounted into the repo server. Challenges include repo fetch load and slow UI so MLB adopts Acuity managed Argo CD agents per cluster and central repo servers, which reduces load and speeds operations.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 2:35How Major League Baseball uses Argo CD
- 5:30Argo CD configuration
- 11:47Secrets
- 16:00MLB App Chart
- 19:30CI Workflows
- 20:36Challenges
- 23:11Roadmap
- 24:42Questions
related talks
18mUnveil the Secret Ingredients for Argo CD in the Enterprise-Scale
34mInfrastructure at Scale Using ArgoCD
26mGitOps Me Some of That! Managing Hundreds of Clusters with Argo CD
26mManaging GitOps Deployments in Multi-cluster Production Environments
24mScaling GitOps Using ArgoCD Application-Sets: Lesson Learnt
05mProject Lightning Talk: Argo CD at Scale: 5 Features You Should Not Miss!
16mProject Update: Argo Project Velocity
27mArgoCD as the Engine of a Brownfield Migration to Kubernetes