Include gitopscluster custom resource so remote clusters join automatically central Argo instance

[alosadagrande]

Hi,

We have been using this custom resource that has been included recently in RHACM that allows provisioned clusters to be managed by the central ArgoCD instance installed in the hub cluster.

Here is a working example of the GitOpsCluster CR that needs to be applied to the management cluster. Once added you need to include the following label into the ManagedCluster CR for every cluster that wants to be managed by the central Argo instance.

I think that with this new CR you can skip some manual steps included in the README that allows to automatically include the recently installed cluster into central ArgoCD. I am not sure where it should be added to your repo since RHACM installation is a requirement. In my forked repository, it is included in the management repo since it is something that is going to be installed in the management cluster, actually inside the config-ztp folder.

Let me know your thoughts.

[williamcaban]

to expand the options and make sure we can cover future extensions of RHACM, would it make sense to define /base/rhacm/ structure and start including these there and update the mgmt-rhacm blueprint to either document in the README how to use or consume the extension, or include it commented out for someone to know of its existence?