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: modules/odc-uninstalling-web-terminal.adoc
+29-7Lines changed: 29 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -31,7 +31,7 @@ Prior to {product-title} 4.8, the Web Terminal Operator used different CRDs to p
31
31
.. Click the Options menu {kebab} for the Web Terminal Operator, and then select *Uninstall Operator*.
32
32
.. In the *Uninstall Operator* confirmation dialog box, click *Uninstall* to remove the Operator, Operator deployments, and pods from the cluster. The Operator stops running and no longer receives updates.
33
33
+
34
-
. Run the following commands to ensure that all `DevWorkspace` CRs created for the Web Terminals are removed.
34
+
. Remove the CRDs used by the Operator.
35
35
+
36
36
[source,terminal]
37
37
----
@@ -55,7 +55,7 @@ The DevWorkspace Operator functions as a standalone Operator and may be required
55
55
====
56
56
57
57
.Procedure
58
-
. Run the following commands to ensure that all `DevWorkspace` CRs are removed along with their related Kubernetes objects, such as deployments.
58
+
. Remove the `DevWorkspace` custom resources used by the Operator, along with any related Kubernetes objects, such as deployments.
If this step is not complete, finalizers make it difficult to fully uninstall the Operator easily.
73
73
====
74
74
+
75
-
. Run the following commands to remove the CRDs:
75
+
. Remove the CRDs used by the Operator:
76
+
+
77
+
[WARNING]
78
+
====
79
+
The DevWorkspace Operator provides custom resource definitions (CRDs) that use conversion webhooks. Failing to remove these CRDs can cause issues on the cluster.
If you remove the `devworkspace-webhook-server` deployment without removing the mutating and validating webhooks, you will not be able use `oc exec` commands to run commands in a container on the cluster. After you remove the webhooks you will be able to use the `oc exec` commands again.
128
+
If you remove the `devworkspace-webhook-server` deployment without removing the mutating and validating webhooks, you will not be able to use `oc exec` commands to run commands in a container on the cluster. After you remove the webhooks you will be able to use the `oc exec` commands again.
107
129
====
108
130
+
109
-
. Run the following commands to remove any lingering services, secrets, and config maps:
131
+
. Remove any remaining services, secrets, and config maps. Depending on the installation, some resources included in the following command may not exist on the cluster.
110
132
+
111
133
[source,terminal]
112
134
----
113
-
$ oc delete all --selector app.kubernetes.io/part-of=devworkspace-operator,app.kubernetes.io/name=devworkspace-webhook-server
135
+
$ oc delete all --selector app.kubernetes.io/part-of=devworkspace-operator,app.kubernetes.io/name=devworkspace-webhook-server -n openshift-operators
0 commit comments