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

Jump to bottom
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

wants to merge 4 commits into from

Conversation

mburke5678
Copy link
Contributor

https://issues.redhat.com/browse/OCPBUGS-44935

Link to docs preview:

QE review:

  • QE has approved this change.

@mburke5678 mburke5678 added this to the Continuous Release milestone Feb 25, 2025
@openshift-ci openshift-ci bot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Feb 25, 2025
@openshift-ci openshift-ci bot added size/M Denotes a PR that changes 30-99 lines, ignoring generated files. and removed size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Feb 25, 2025
@mburke5678
Copy link
Contributor Author

@jrvaldes PTAL

@ocpdocs-previewbot
Copy link

ocpdocs-previewbot commented Feb 25, 2025 •
edited
Loading

🤖 Thu Feb 27 21:18:47 - Prow CI generated the docs preview:

https://89121--ocpdocs-pr.netlify.app/

jrvaldes
jrvaldes reviewed Feb 25, 2025
View reviewed changes
modules/deleting-wmco-namespace.adoc Outdated
Comment on lines 20 to 24
. 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.

jrvaldes
jrvaldes reviewed Feb 25, 2025
View reviewed changes
modules/deleting-wmco-namespace.adoc Outdated
+
[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

@openshift-ci OpenShift CI
Copy link

openshift-ci bot commented Feb 27, 2025

@mburke5678: all tests passed!

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@mburke5678
Copy link
Contributor Author

@rrasouli Can you please take a look at this PR?

@mburke5678 mburke5678 changed the title OCPBUGS44935: Issue in file windows_containers/disabling-windows-container-workloads.adoc OCPBUGS44935: WMCO uninstall should describe procedure of unistalling the operator and deleteing the namespace Mar 5, 2025
@mburke5678 mburke5678 changed the title OCPBUGS44935: WMCO uninstall should describe procedure of unistalling the operator and deleteing the namespace OCPBUGS44935: WMCO uninstall should describe procedure of uninstalling the operator and deleteing the namespace Mar 17, 2025
@rrasouli
Copy link

This is not the correct procedure, the only method that is working:

  1. creating a new project e.g new-namespace with monitoring enabled
  2. uninstalling from web-console existing WMCO
  3. installing new operator on the new project e.g new-namespace instead of openshift-windows-machine-config-operator namespace
    I do not recommend that users will do all these actions from CLI, they might have hit bug https://issues.redhat.com/browse/OCPBUGS-46473

@mburke5678
Copy link
Contributor Author

@rrasouli I don't think what you stated above is the use case for this PR and the Jira associated with it. I think the idea is to better document the full removal of the WMCO operator and components. No re-install.
@jrvaldes WDYT?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@jrvaldes jrvaldes jrvaldes left review comments

Assignees
No one assigned
Labels
branch/enterprise-4.12 branch/enterprise-4.14 branch/enterprise-4.15 branch/enterprise-4.16 branch/enterprise-4.17 branch/enterprise-4.18 branch/enterprise-4.19 size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Milestone
Continuous Release
Development

Successfully merging this pull request may close these issues.
4 participants
@mburke5678 @ocpdocs-previewbot @rrasouli @jrvaldes