Add info about singleArgoCD

Author: mbaldessari

content/learn/getting-started-multi-cloud-gitops.adoc

@@ -214,12 +214,12 @@ To know the cluster group name for the patterns that you want to deploy, check t
 +
 [NOTE]
 ====
-A pop-up error with the message "Oh no! Something went wrong." might appear during the process. This error can be safely disregarded as it does not impact the installation of the Multicloud GitOps pattern. Use the Hub ArgoCD UI, accessible through the nines menu, to check the status of ArgoCD instances, which will display states such as progressing, healthy, and so on, for each managed application. The Cluster ArgoCD provides detailed status on each application, as defined in the clustergroup values file.
+A pop-up error with the message "Oh no! Something went wrong." might appear during the process. This error can be safely disregarded as it does not impact the installation of the Multicloud GitOps pattern. Use the ArgoCD UI, accessible through the nines menu, to check the status of ArgoCD applications, which displays states such as progressing, healthy, and so on, for each managed application.
 ====
 
 The {rh-gitops} Operator displays in list of *Installed Operators*. The {rh-gitops} Operator installs the remaining assets and artifacts for this pattern. To view the installation of these assets and artifacts, such as {rh-rhacm-first}, ensure that you switch to *Project:All Projects*.
 
-Wait some time for everything to deploy. You can track the progress through the `Hub ArgoCD` UI from the nines menu. The `config-demo` project  appears stuck in a `Degraded` state. This is the expected behavior when installing using the OpenShift Container Platform console.
+Wait some time for everything to deploy. You can track the progress through the ArgoCD UI from the nines menu. The `config-demo` project  appears stuck in a `Degraded` state. This is the expected behavior when installing using the OpenShift Container Platform console.
 
 * To resolve this you need to run the following to load the secrets into the vault:
 +

content/learn/values-global-configuration.adoc

@@ -35,6 +35,22 @@ global:
 
 Do not change this value unless you are creating a new pattern.
 
+[id="global-singleargocd"]
+=== `global.singleArgoCD`
+
+Controls whether the pattern uses a single Argo CD instance for all managed objects. By default, the framework deploys two Argo CD instances: a clusterwide instance for privileged resources such as namespaces and subscriptions, and a namespaced instance for pattern applications. Setting this flag to `true` consolidates everything into the single clusterwide instance.
+
+[source,yaml]
+----
+global:
+  singleArgoCD: true
+----
+
+[IMPORTANT]
+====
+Use this flag only for new installs. Setting `singleArgoCD` to `true` on an existing deployment that already has two Argo CD instances is unlikely to work.
+====
+
 [id="global-options"]
 === `global.options`
 
@@ -129,6 +145,7 @@ The following example shows a typical `values-global.yaml` file for the Multiclo
 ---
 global:
   pattern: multicloud-gitops
+  singleArgoCD: true
 
   options:
     useCSV: false
@@ -142,7 +159,7 @@ main:
     enabled: true
 ----
 
-For most patterns, the default values provide a working configuration. Customize specific fields only when your environment requires different behavior, such as pinning operator versions or deploying in a disconnected environment.
+For most patterns, the default values provide a working configuration. Customize specific fields only when your environment requires different behavior, such as pinning operator versions, using a single Argo CD instance, or deploying in a disconnected environment.
 
 [id="additional-resources"]
 == Additional resources

modules/mcg-deploying-mcg-pattern.adoc

@@ -201,12 +201,12 @@ To know the cluster group name for the patterns that you want to deploy, check t
 +
 [NOTE]
 ====
-A pop-up error with the message "Oh no! Something went wrong." might appear during the process. This error can be safely disregarded as it does not impact the installation of the Multicloud GitOps pattern. Use the Hub ArgoCD UI, accessible through the nines menu, to check the status of ArgoCD instances, which will display states such as progressing, healthy, and so on, for each managed application. The Cluster ArgoCD provides detailed status on each application, as defined in the clustergroup values file.
+A pop-up error with the message "Oh no! Something went wrong." might appear during the process. This error can be safely disregarded as it does not impact the installation of the Multicloud GitOps pattern. Use the ArgoCD UI, accessible through the nines menu, to check the status of ArgoCD applications, which displays states such as progressing, healthy, and so on, for each managed application.
 ====
 
 The *{rh-gitops} Operator* displays in list of *Installed Operators*. The *{rh-gitops} Operator* installs the remaining assets and artifacts for this pattern. To view the installation of these assets and artifacts, such as *{rh-rhacm-first}*, ensure that you switch to *Project:All Projects*.
 
-Wait some time for everything to deploy. You can track the progress through the `Hub ArgoCD` UI from the nines menu. The `config-demo` project  appears stuck in a `Degraded` state. This is the expected behavior when installing using the OpenShift Container Platform console.
+Wait some time for everything to deploy. You can track the progress through the ArgoCD UI from the nines menu. The `config-demo` project  appears stuck in a `Degraded` state. This is the expected behavior when installing using the OpenShift Container Platform console.
 
 * To resolve this you need to run the following to load the secrets into the vault:
 +