Initial setup
Almost all of the tutorials, blogs, and articles out there discuss installing Argo CD in the argocd namespace, and it does make sense as it is a specific namespace—it will not collide with other applications. But there are cases when that might not be possible—I am talking about when multiple instances of Argo CD are installed in the same Kubernetes cluster. This is a valid scenario when we want to split clusters that an Argo CD instance is managing, such as one that takes care of prod clusters and another the non-prod ones. Another scenario could be when they take care of the same clusters but only specific namespaces from it, so a model of an Argo CD instance per team. We will follow the scenario with prod and non-prod installations.
When we have two or more Argo CD installations in the same cluster, there are a couple of things we need to pay attention to. First is the fact that when we install it in the cluster, there are some Custom Resource Definitions...
