[RFE] Explore resource utilization of remote in-cluster ArgoCD #17
Description
In non-dense clusters (like Core and non-DU clusters), it is possible to use an in-cluster ArgoCD instance to do pull of configurations. This model removes dependencies on a centralized instance and allow for highly distributable and scalable GitOps model.
The main caveats that need to be addressed for this model are:
- the unknown resource utilization brackets to make this work on a cluster based on number of nodes, MCPs and CNFs
- the lack of centralized visibility to be aware of the status of each clusters. This could be address by RHACM but need to be documented and tested?
- how to maintain hierarchical GitOps model between organization desired configurations vs localized customizations?
- when can a centralized deployment GitOps be used in conjunction to a distributed in-cluster config & operations GitOps?