You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/Migration_Guide.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ For understanding the differences between [Argo CD Community Operator](https://g
6
6
7
7
**Note**: Installing GitOps operator will create a namespace with the name `openshift-gitops` and an Argo CD instance in the same namespace. This instance can be used for managing your OpenShift cluster configuration. It is enabled with Dex OpenShift connector by default which allows users to log in with their OpenShift credentials.
8
8
9
-
The default Argo CD instance in the `openshift-gitops` namespace can be deleted by adding an environmental variable `DISABLE_DEFAULT_ARGOCD_INSTANCE` with the value `true` in the Subscription resource.
9
+
The default Argo CD instance and the `openshift-gitops` namespace can be deleted by adding an environmental variable `DISABLE_DEFAULT_ARGOCD_INSTANCE` with the value `true` in the Subscription resource. This will completely remove the default installation.
10
10
11
11
To disable the default instance, edit the Subscription and add the following:
12
12
@@ -65,7 +65,7 @@ Post migration the above environment variables has to be copied to GitOps operat
65
65
66
66
**Note**:
67
67
GitOps operator supports the below additional environment variables
68
-
`DISABLE_DEFAULT_ARGOCD_INSTANCE`: Disables the installation of default instance in openshift-gitops namespace.
68
+
`DISABLE_DEFAULT_ARGOCD_INSTANCE`: Disables the installation of default instance in openshift-gitops namespace. This prevents the creation of the `openshift-gitops` namespace and ArgoCD instance. If they already exist, they will be deleted.
69
69
70
70
`ARGOCD_CLUSTER_CONFIG_NAMESPACES`: Argo CD is granted permissions to manage specific cluster-scoped resources which include
71
71
platform operators, optional OLM operators, user management, etc. Argo CD is not granted cluster-admin. You can find the complete
Copy file name to clipboardExpand all lines: docs/OpenShift GitOps Usage Guide.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -121,7 +121,7 @@ When installing the OpenShift GitOps operator to ROSA/OSD, cluster administrator
121
121
122
122
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.
123
123
124
-
**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.
124
+
**Warning**: setting this option to true will cause the existing Argo CD instance **and the `openshift-gitops` namespace** to be deleted. This completely removes the default installation. Argo CD instances in other namespaces should not be affected.
125
125
126
126
On OpenShift Console, go to
127
127
@@ -222,7 +222,7 @@ Updating the following environment variables in the existing Subscription Object
222
222
<tr>
223
223
<td>DISABLE_DEFAULT_ARGOCD_INSTANCE</td>
224
224
<td>false</td>
225
-
<td>When set to `true`, will disable the default 'ready-to-use' installation of Argo CD in `openshift-gitops` namespace.</td>
225
+
<td>When set to `true`, will disable the default 'ready-to-use' installation of Argo CD in `openshift-gitops` namespace. This prevents the creation of the `openshift-gitops` namespace and ArgoCD instance. If the namespace already exists, it will be deleted along with the ArgoCD instance.</td>
Copy file name to clipboardExpand all lines: hack/non-olm-install/README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -81,7 +81,7 @@ The following environment variables can be set to configure various options for
81
81
| ----------- | ----------- |------------- |
82
82
|**ARGOCD_CLUSTER_CONFIG_NAMESPACES**|OpenShift GitOps instances in the identified namespaces are granted limited additional permissions to manage specific cluster-scoped resources, which include platform operators, optional OLM operators, user management, etc.Multiple namespaces can be specified via a comma delimited list. | openshift-gitops |
83
83
|**CONTROLLER_CLUSTER_ROLE**| This environment variable enables administrators to configure a common cluster role to use across all managed namespaces in the role bindings the operator creates for the Argo CD application controller. | None |
84
-
|**DISABLE_DEFAULT_ARGOCD_INSTANCE**| When set to `true`, this will disable the default 'ready-to-use' installation of Argo CD in the `openshift-gitops` namespace. |false |
84
+
|**DISABLE_DEFAULT_ARGOCD_INSTANCE**| When set to `true`, this will disable the default 'ready-to-use' installation of Argo CD in the `openshift-gitops` namespace. This prevents the creation of the `openshift-gitops` namespace and ArgoCD instance. If they already exist, they will be deleted. |false |
85
85
|**SERVER_CLUSTER_ROLE**|This environment variable enables administrators to configure a common cluster role to use across all of the managed namespaces in the role bindings the operator creates for the Argo CD server. | None |
86
86
|**WATCH_NAMESPACE**| namespaces in which Argo applications can be created | None |
87
87
|**ENABLE_CONVERSION_WEBHOOK**| This environment variable enables conversion webhook to convert v1alpha1 ArgoCD resources to v1beta1 | true |
0 commit comments