From e6a680d94f548c5c15c802214634d7494da1160e Mon Sep 17 00:00:00 2001
From: abhishek pareek <makeittotop@gmail.com>
Date: Wed, 7 Dec 2022 04:14:30 -0800
Subject: [PATCH] clearer instruction to disable default argocd instance

Clearly mentioning the `env` resource within the `subscriptions.operators.coreos.com.spec.config` CRD to add the associated env. var. leading to disabling the default argocd  instance launch
---
 docs/OpenShift GitOps Usage Guide.md | 15 ++++++++++++++-
 1 file changed, 14 insertions(+), 1 deletion(-)

diff --git a/docs/OpenShift GitOps Usage Guide.md b/docs/OpenShift GitOps Usage Guide.md
index 0d8876a9922..dab43885297 100644
--- a/docs/OpenShift GitOps Usage Guide.md	
+++ b/docs/OpenShift GitOps Usage Guide.md	
@@ -119,7 +119,20 @@ openshift-gitops-server-86df579bbf-zz9lx                     1/1     Running   0
 
 When installing the OpenShift GitOps operator to ROSA/OSD, cluster administrators may wish to exclude users from modifying resources within the *openshift-** namespaces, including the *openshift-gitops* namespace which is the default location for an Argo CD install.
 
-To disable the default ‘ready-to-use’ installation of Argo CD: as an admin, update the existing Subscription Object for Gitops Operator and add `DISABLE_DEFAULT_ARGOCD_INSTANCE = true` to the spec.
+To disable the default ‘ready-to-use’ installation of Argo CD: as an admin, update the existing Subscription Object for Gitops Operator and add `DISABLE_DEFAULT_ARGOCD_INSTANCE = true` to the `subscriptions.operators.coreos.com.spec.config.env` resource as follows - 
+
+```
+apiVersion: operators.coreos.com/v1alpha1
+kind: Subscription
+  name: openshift-gitops-operator
+  namespace: openshift-operators
+spec:
+  config:
+    env:
+    - name: DISABLE_DEFAULT_ARGOCD_INSTANCE
+      value: "TRUE"
+
+```
 
 **Warning**: setting this option to true will cause the existing Argo CD install in the *openshift-gitops* namespace to be deleted. Argo CD instances in other namespaces should not be affected.