Uninstalling OKD Virtualization
You uninstall OKD Virtualization by using the web console or the command line interface (CLI) to delete the OKD Virtualization workloads, the Operator, and its resources.
Uninstalling OKD Virtualization by using the web console
You uninstall OKD 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 OKD Virtualization while its workloads remain on the cluster. |
Deleting the HyperConverged custom resource
To uninstall OKD Virtualization, you first delete the HyperConverged
custom resource (CR).
Prerequisites
- You have access to an OKD cluster using an account with
cluster-admin
permissions.
Procedure
Navigate to the Operators → Installed Operators page.
Select the OKD Virtualization Operator.
Click the OKD Virtualization Deployment tab.
Click the Options menu beside
kubevirt-hyperconverged
and select Delete HyperConverged.Click Delete in the confirmation window.
Deleting Operators from a cluster using the web console
Cluster administrators can delete installed Operators from a selected namespace by using the web console.
Prerequisites
- You have access to an OKD cluster web console using an account with
cluster-admin
permissions.
Procedure
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.
Deleting a namespace using the web console
You can delete a namespace by using the OKD web console.
Prerequisites
- You have access to an OKD cluster using an account with
cluster-admin
permissions.
Procedure
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.
Deleting OKD Virtualization custom resource definitions
You can delete the OKD Virtualization custom resource definitions (CRDs) by using the web console.
Prerequisites
- You have access to an OKD cluster using an account with
cluster-admin
permissions.
Procedure
Navigate to Administration → CustomResourceDefinitions.
Select the Label filter and enter
operators.coreos.com/kubevirt-hyperconverged.openshift-cnv
in the Search field to display the OKD Virtualization CRDs.Click the Options menu beside each CRD and select Delete CustomResourceDefinition.
Uninstalling OKD Virtualization by using the CLI
You can uninstall OKD Virtualization by using the OpenShift CLI (oc
).
Prerequisites
You have access to an OKD 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 OKD Virtualization while its workloads remain on the cluster.
Procedure
Delete the
HyperConverged
custom resource:$ oc delete HyperConverged kubevirt-hyperconverged -n openshift-cnv
Delete the OKD Virtualization Operator subscription:
$ oc delete subscription kubevirt-hyperconverged -n openshift-cnv
Delete the OKD Virtualization
ClusterServiceVersion
resource:$ oc delete csv -n openshift-cnv -l operators.coreos.com/kubevirt-hyperconverged.openshift-cnv
List the OKD Virtualization custom resource definitions (CRDs) by running the
oc delete crd
command with thedry-run
option:$ oc delete crd --dry-run=client -l operators.coreos.com/kubevirt-hyperconverged.openshift-cnv
Example output
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 thedry-run
option:$ oc delete crd -l operators.coreos.com/kubevirt-hyperconverged.openshift-cnv
Additional resources