Azure

Scaling ArgoCD to 3000+ Applications: HA and Multi-Cluster Sharding

As organizations grow, so does their GitOps footprint. Managing a couple dozen applications with ArgoCD is a walk in the park — you install it, point it at your repo, and everything just works. It’s beautiful. You start bragging about GitOps on Reddit. Life is good. Then you hit 3,000+ applications across dozens of Kubernetes clusters. Suddenly, reconciliation loops take forever. The UI feels like it’s running on a potato. The application-controller starts getting OOM-killed at 3 AM, and your on-call engineer is questioning their career choices. Your Slack channel fills up with “is ArgoCD down again?” messages, and you start wondering if maybe spreadsheets were fine all along.