Ce contenu n'est pas disponible dans la langue sélectionnée.
Chapter 11. 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.
11.1. Uninstalling the Windows Machine Config Operator
You can uninstall the Windows Machine Config Operator (WMCO) from your cluster.
Prerequisites
- 
						Delete the Windows Machineobjects hosting your Windows workloads.
Procedure
- 
						From the Operators OperatorHub page, use the Filter by keyword box to search for Red Hat Windows Machine Config Operator.
- Click the Red Hat Windows Machine Config Operator tile. The Operator tile indicates it is installed.
- In the Windows Machine Config Operator descriptor page, click Uninstall.
11.2. Deleting the Windows Machine Config Operator namespace
You can delete the namespace that was generated for the Windows Machine Config Operator (WMCO) by default.
Prerequisites
- The WMCO is removed from your cluster.
Procedure
- Remove all Windows workloads that were created in the - openshift-windows-machine-config-operatornamespace:- oc delete --all pods --namespace=openshift-windows-machine-config-operator - $ oc delete --all pods --namespace=openshift-windows-machine-config-operator- Copy to Clipboard Copied! - Toggle word wrap Toggle overflow 
- Verify that all pods in the - openshift-windows-machine-config-operatornamespace are deleted or are reporting a terminating state:- oc get pods --namespace openshift-windows-machine-config-operator - $ oc get pods --namespace openshift-windows-machine-config-operator- Copy to Clipboard Copied! - Toggle word wrap Toggle overflow 
- Delete the - openshift-windows-machine-config-operatornamespace:- oc delete namespace openshift-windows-machine-config-operator - $ oc delete namespace openshift-windows-machine-config-operator- Copy to Clipboard Copied! - Toggle word wrap Toggle overflow