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

Changes from 2 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
39 changes: 34 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,60 @@

:_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 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
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what is the recommendation here, to remove all pods or the namespace with all the resources?

Copy link
Contributor Author

@mburke5678 mburke5678 Feb 26, 2025 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jrvaldes This was your recommendation. We are deleting the WMCO-related pods in that namespace. The following steps delete resources and finally the namespace itself.

----

. 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
----

. Delete the `openshift-windows-machine-config-operator` namespace:
. Delete the subscription by using the following command:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I recommend following the Deleting Operators from a cluster using the CLI as per existing docs

https://docs.openshift.com/container-platform/4.18/operators/admin/olm-deleting-operators-from-cluster.html#olm-deleting-operator-from-a-cluster-using-cli_olm-deleting-operators-from-a-cluster

+
[source,terminal]
----
$ oc delete subscription -n openshift-windows-machine-config-operator windows-machine-config-operator
----

. Delete the CSV by using the following command:
+
[source,terminal]
----
$ oc delete csv -n openshift-windows-machine-config-operator ${WMCO_CSV}
----

. 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 by using the following command:
+
[source,terminal]
----
Expand Down