Skip to content

OCPBUGS44935: WMCO uninstall should describe procedure of uninstalling the operator and deleteing the namespace #89121

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 4 commits into
base: main
Choose a base branch
from
Open

OCPBUGS44935: WMCO uninstall should describe procedure of uninstalling the operator and deleteing the namespace #89121

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
0e5b179
edit
Feb 17, 2025
044305e
edits per jose
Feb 25, 2025
827a7b8
edits
Feb 27, 2025
d356bb0
edits from testing
Feb 27, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
36 changes: 31 additions & 5 deletions modules/deleting-wmco-namespace.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,31 +4,57 @@

:_mod-docs-content-type: PROCEDURE
[id="deleting-wmco-namespace_{context}"]
= Deleting the Windows Machine Config Operator namespace
= Deleting the Windows Machine Config Operator namespace and operands

You can delete the namespace that was generated for the Windows Machine Config Operator (WMCO) by default.
After removing the Windows Machine Config Operator, it is recommended that you remove the other components associated with the Operator to avoid potential issues.

.Prerequisites

* The Windows `Machine` objects that hosted your Windows workloads are removed from your cluster.
* The WMCO is removed from your cluster.

.Procedure

. Remove all Windows workloads that were created in the `openshift-windows-machine-config-operator` namespace:
This procedure assumes that you are using the default `openshift-windows-machine-config-operator` namespace.

. Remove all WMCO resources that were created in the `openshift-windows-machine-config-operator` namespace by using the following command:
+
[source,terminal]
----
$ oc delete --all pods --namespace=openshift-windows-machine-config-operator
----
+
[NOTE]
====
The `openshift-windows-machine-config-operator` namespace is reserved for WMCO resources. There should be no Windows workloads or pods in the namespace.
====

. Verify that all pods in the `openshift-windows-machine-config-operator` namespace are deleted or are reporting a terminating state:
. Verify that all pods in the `openshift-windows-machine-config-operator` namespace are deleted or are reporting a terminating state by using the following command:
+
[source,terminal]
----
$ oc get pods --namespace openshift-windows-machine-config-operator
----
+
.Example output
[source,terminal]
----
No resources found in openshift-windows-machine-config-operator namespace.
----

. Delete RBAC resources by using the following command:
+
[source,terminal]
----
$ oc delete clusterrolebinding windows-instance-config-daemon
----
+
[source,terminal]
----
$ oc delete clusterroles windows-instance-config-daemon
----

. Delete the `openshift-windows-machine-config-operator` namespace:
. Delete the `openshift-windows-machine-config-operator` namespace by using the following command:
+
[source,terminal]
----
Expand Down
2 changes: 1 addition & 1 deletion modules/uninstalling-wmco.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ You can uninstall the Windows Machine Config Operator (WMCO) from your cluster.

.Procedure

. From the *Operators -> OperatorHub* page, use the *Filter by keyword* box to search for `Red Hat Windows Machine Config Operator`.
. From the *Operators -> OperatorHub* page, use the *Filter by keyword* box to search for `Windows Machine Config Operator`.

. Click the *Red Hat Windows Machine Config Operator* tile. The Operator tile indicates it is installed.

Expand Down