$ oc delete HyperConverged kubevirt-hyperconverged -n openshift-cnv
You uninstall OpenShift Virtualization by using the web console or the command line interface (cli) to delete the OpenShift Virtualization workloads, the Operator, and its resources.
You uninstall OpenShift Virtualization by using the web console to perform the following tasks:
You must first delete all virtual machines, and virtual machine instances. You cannot uninstall OpenShift Virtualization while its workloads remain on the cluster. |
To uninstall OpenShift Virtualization, you first delete the HyperConverged
custom resource (CR).
You have access to an Red Hat OpenShift Service on AWS cluster using an account with cluster-admin
permissions.
Navigate to the Operators → Installed Operators page.
Select the OpenShift Virtualization Operator.
click the OpenShift Virtualization Deployment tab.
click the Options menu beside kubevirt-hyperconverged
and select Delete HyperConverged.
click Delete in the confirmation window.
Cluster administrators can delete installed Operators from a selected namespace by using the web console.
You have access to an Red Hat OpenShift Service on AWS cluster web console using an account with
dedicated-admin
permissions.
Navigate to the Operators → Installed Operators page.
Scroll or enter a keyword into the Filter by name field to find the Operator that you want to remove. Then, click on it.
On the right side of the Operator Details page, select Uninstall Operator from the Actions list.
An Uninstall Operator? dialog box is displayed.
Select Uninstall to remove the Operator, Operator deployments, and pods. Following this action, the Operator stops running and no longer receives updates.
This action does not remove resources managed by the Operator, including custom resource definitions (CRDs) and custom resources (CRs). Dashboards and navigation items enabled by the web console and off-cluster resources that continue to run might need manual clean up. To remove these after uninstalling the Operator, you might need to manually delete the Operator CRDs. |
You can delete a namespace by using the Red Hat OpenShift Service on AWS web console.
You have access to an Red Hat OpenShift Service on AWS cluster using an account with cluster-admin
permissions.
Navigate to Administration → Namespaces.
Locate the namespace that you want to delete in the list of namespaces.
On the far right side of the namespace listing, select Delete Namespace from the Options menu .
When the Delete Namespace pane opens, enter the name of the namespace that you want to delete in the field.
click Delete.
You can delete the OpenShift Virtualization custom resource definitions (CRDs) by using the web console.
You have access to an Red Hat OpenShift Service on AWS cluster using an account with cluster-admin
permissions.
Navigate to Administration → CustomResourceDefinitions.
Select the Label filter and enter operators.coreos.com/kubevirt-hyperconverged.openshift-cnv
in the Search field to display the OpenShift Virtualization CRDs.
click the Options menu beside each CRD and select Delete CustomResourceDefinition.
You can uninstall OpenShift Virtualization by using the OpenShift cli (oc
).
You have access to an Red Hat OpenShift Service on AWS cluster using an account with cluster-admin
permissions.
You have installed the OpenShift cli (oc
).
You have deleted all virtual machines and virtual machine instances. You cannot uninstall OpenShift Virtualization while its workloads remain on the cluster.
Delete the HyperConverged
custom resource:
$ oc delete HyperConverged kubevirt-hyperconverged -n openshift-cnv
Delete the OpenShift Virtualization Operator subscription:
$ oc delete subscription kubevirt-hyperconverged -n openshift-cnv
Delete the OpenShift Virtualization ClusterServiceVersion
resource:
$ oc delete csv -n openshift-cnv -l operators.coreos.com/kubevirt-hyperconverged.openshift-cnv
Delete the OpenShift Virtualization namespace:
$ oc delete namespace openshift-cnv
List the OpenShift Virtualization custom resource definitions (CRDs) by running the oc delete crd
command with the dry-run
option:
$ oc delete crd --dry-run=client -l operators.coreos.com/kubevirt-hyperconverged.openshift-cnv
customresourcedefinition.apiextensions.k8s.io "cdis.cdi.kubevirt.io" deleted (dry run) customresourcedefinition.apiextensions.k8s.io "hostpathprovisioners.hostpathprovisioner.kubevirt.io" deleted (dry run) customresourcedefinition.apiextensions.k8s.io "hyperconvergeds.hco.kubevirt.io" deleted (dry run) customresourcedefinition.apiextensions.k8s.io "kubevirts.kubevirt.io" deleted (dry run) customresourcedefinition.apiextensions.k8s.io "networkaddonsconfigs.networkaddonsoperator.network.kubevirt.io" deleted (dry run) customresourcedefinition.apiextensions.k8s.io "ssps.ssp.kubevirt.io" deleted (dry run) customresourcedefinition.apiextensions.k8s.io "tektontasks.tektontasks.kubevirt.io" deleted (dry run)
Delete the CRDs by running the oc delete crd
command without the dry-run
option:
$ oc delete crd -l operators.coreos.com/kubevirt-hyperconverged.openshift-cnv