Anyone scaling ArgoCD across multiple clusters?

I’ve been using ArgoCD with GitHub Actions for GitOps, and it worked well in the beginning. But once I started managing multiple clusters, it got more complicated:

- Syncs slowed down

- Had to spin up separate ArgoCD instances

- CI/CD felt disconnected from the GitOps flow

Would like to hear how others have approached GitOps at scale. Did you stick with Argo and layer on tooling? Or move to something like Flux or a custom setup? Any lessons learned are welcome.

evrflx · 4 months ago

I used one ArgoCD instance per cluster as of today. Makes security and scaling easier. What is your main driver to have a single ArgoCD instance?

DeborahEmeni_ · 4 months ago

got it, that makes sense. i was trying to keep things centralized at first but splitting per cluster might be the better call. did you end up automating anything around managing those separate instances or mostly manual?