Description:
The current RHACM documentation includes guidance for configuring GitOps (e.g., Argo CD) with a regular ACM Hub. However, it lacks documentation on how to configure GitOps workflows in the context of Global Hub, where Hub clusters are attached to the Global Hub, and each Hub cluster manages its own set of spoke/managed clusters.

Impact:

• Users familiar with GitOps on a single RHACM Hub are unable to translate the same model to a Global Hub architecture.

• No clarity on where GitOps components (e.g., Argo CD instances) should live in a multi-hub setup.

• Inability to scale GitOps consistently across multiple hubs and managed clusters.

• Increased complexity in managing GitOps workflows and policies at global scale.

Expected Documentation Content:

• Overview of GitOps models (push/pull) in RHACM and how these extend to Global Hub topologies.

• Architecture guidance for multi-hub/multi-cluster GitOps configuration.

• Deployment models for GitOps components (Argo CD at each Hub, or centralized).

• Sample manifests/YAMLs, Git repo layout strategies.

• Integration with RHACM Global Hub features (e.g., policy status aggregation).

• Best practices for scalability, observability, and security.

2. - [ ] Mandatory: Choose the type of documentation change or review.

• [ ] We need a whole new section; this is a function not
  documented before and doesn't belong in any current section

3. - [ ] Mandatory: Find the link to where the documentation update
should go and add it to the recommended changes. You can either use the
published doc or the staged repo for this step:

Note: As the feature and doc is understood, this recommendation may
change. If this is new documentation, link to the section where you think
it should be placed.

Customer Portal published version

https://docs.redhat.com/en/documentation/red_hat_advanced_cluster_management_for_kubernetes/2.13/html-single/gitops/index#gitops-overview

Doc staged repo within the ACM Workspace:
https://github.com/stolostron/rhacm-docs