LinkedIn recently replaced Argo CD with a custom GitOps engine that deploys across more than 250 Kubernetes clusters and handles over 100,000 deployments a week. The scale is unusual, but the underlying friction is not. Teams running dozens of clusters against one Argo CD instance eventually hit the same walls: reconciliation lag, app sprawl, and webhooks that stop telling the truth.
By the end of this article you will know which limits you will actually hit, how to push them back, and when a custom controller is genuinely justified.
Where vanilla Argo CD strains first
Argo CD watches Git repositories and reconciles cluster state against them. The strain shows up in three predictable places as you grow:
Application count. Each Application object is a controller reconcile target. Past a few thousand, the controller's reconcile queue slows down and drift detection lags behind commits.
Webhook fan-out. One commit to a shared config repo can touch hundreds of Applications.…