argocd-application-controller OOMKilled despite sharding — how to size shards correctly
Our Argo CD instance manages several thousand resources across multiple clusters, and the argocd-application-controller pod keeps getting OOMKilled as its memory climbs steadily over hours. From the documentation and metrics, this looks like the informer/watch cache growing with the number of live managed objects rather than a classic leak, but the restarts
argocd