Two different ArgoCD instances for managing the same set of clusters

[LiorLieberman]

Has anyone ever tried or heard of a usecase where two ArgoCD instances (installed on different clusters) manage the same set of clusters ?
"manage" means they are able to deploy application to the same set of clusters.

Is this encouraged, or even possible?

[FernandoMiguel]

we have done it, during blue/green deployments of argo.
works fine, as long as the charts are the same.
one time there was a tiny issue in annotations between argo versions and that cause drift.
but other than that, argo is able to adopt existing resources based on annotations just fine

and if you dont want them to manage the same set of apps, even less problematic it is

[LiorLieberman]

Thanks for the input.
I brought it in the contributors meeting as well - seems like this pattern, when used is mostly for migrations from one argo to another. (or blue/green of argo) as you said.

And of course, the key thing is that the charts must be the same.

I am interested to learn if anyone had encountered a usecase where people use this specifically for a different purpose than migration.

[jkleinlercher]

@LiorLieberman did you then use this option in real use cases? I can think of a high-availability / multi-cloud topology where you want to use this pattern. However, I never tried this and so I don't have any experience with this.

[LiorLieberman]

I did not