Skip to content

Disabling Windows container workloads

You can disable the capability to run Windows container workloads by uninstalling the Windows Machine Config Operator (WMCO) and deleting the namespace that was added by default when you installed the WMCO.

Uninstalling the Windows Machine Config Operator

If you want to disable the capability to run Windows container workloads, you can uninstall the Windows Machine Config Operator (WMCO) from your cluster.

Prerequisites

  • Delete the Windows Machine objects hosting your Windows workloads.

Procedure

  1. From the Ecosystem → Software Catalog page, use the Filter by keyword box to search for Red Hat Windows Machine Config Operator.
  2. Click the Red Hat Windows Machine Config Operator tile. The Operator tile indicates it is installed.
  3. In the Windows Machine Config Operator descriptor page, click Uninstall.

Deleting the Windows Machine Config Operator namespace

If you want to disable the capability to run Windows container workloads, after you uninstall the Windows Machine Config Operator (WMCO), you can delete the namespace that was generated by default for the WMCO.

Prerequisites

  • The WMCO is removed from your cluster.

Procedure

  1. Remove all Windows workloads that were created in the openshift-windows-machine-config-operator namespace:

    $ oc delete --all pods --namespace=openshift-windows-machine-config-operator

  2. Verify that all pods in the openshift-windows-machine-config-operator namespace are deleted or are reporting a terminating state:

    $ oc get pods --namespace openshift-windows-machine-config-operator

  3. Delete the openshift-windows-machine-config-operator namespace:

    $ oc delete namespace openshift-windows-machine-config-operator

Additional resources