Chapter 1. Container-native virtualization installation

Procedure

1. From the OpenShift Container Platform web console, navigate to the Administration Namespaces page.
2. Click Create Namespace.
3. In the Name field, type openshift-cnv.
4. Click Create.

Procedure

1. Navigate to the Operators Installed Operators page.
2. Click KubeVirt HyperConverged Cluster Operator.

3. Click the KubeVirt HyperConverged Cluster Operator Deployment tab and click Create HyperConverged.

   1. After you click Create HyperConverged, a YAML file is displayed. Remove the single quotation marks around the word 'false'. This is a workaround for the issue reported in BZ#1767167.

      When it is initially displayed, the YAML file resembles the following example:

      apiVersion: hco.kubevirt.io/v1alpha1
      kind: HyperConverged
      metadata:
        name: kubevirt-hyperconverged
        namespace: openshift-cnv
      spec:
        BareMetalPlatform: 'false' 1

      1

      Ensure that this line reads BareMetalPlatform: false before proceeding to the next step.

4. Click Create to launch container-native virtualization.
5. Navigate to the Workloads Pods page and monitor the container-native virtualization Pods until they are all Running. After all the Pods display the Running state, you can access container-native virtualization.

Procedure

1. Run the following command:

   $ oc get csv

2. Review the output, checking the PHASE field. For example:

   VERSION  REPLACES                                        PHASE
   2.1.1    kubevirt-hyperconverged-operator.v2.1.0         Installing
   2.1.0                                                    Replacing

3. Optional: Monitor the aggregated status of all container-native virtualization component conditions by running the following command:

   $ oc get hco -n openshift-cnv hyperconverged-cluster \
   -o=jsonpath='{range .status.conditions[*]}{.type}{"\t"}{.status}{"\t"}{.message}{"\n"}{end}'

   A successful upgrade results in the following output:

   ReconcileComplete  True  Reconcile completed successfully
   Available          True  Reconcile completed successfully
   Progressing        False Reconcile completed successfully
   Degraded           False Reconcile completed successfully
   Upgradeable        True  Reconcile completed successfully

Procedure

1. From the OpenShift Container Platform web console, select openshift-cnv from the Projects list.
2. Navigate to the Operators Installed Operators page.
3. Click KubeVirt HyperConverged Cluster Operator.
4. Click the KubeVirt HyperConverged Cluster Operator Deployment tab.
5. Click the Options menu in the row containing the hyperconverged-cluster custom resource. In the expanded menu, click Delete HyperConverged.
6. Click Delete in the confirmation window.
7. Navigate to the Workloads Pods page to verify that only the Operator Pods are running.

8. Open a terminal window and clean up the remaining KubeVirt resources by running the following command:

   $ oc delete apiservices v1alpha3.subresources.kubevirt.io -n openshift-cnv

   Note

   Because some KubeVirt resources are currently improperly retained, you must manually remove them. These resources will be removed automatically after (BZ1712429) is resolved.

Procedure

1. Navigate to the Catalog OperatorHub page.
2. Locate the KubeVirt HyperConverged Cluster Operator and then select it.
3. Click Uninstall.

Procedure

1. Navigate to Administration Namespaces.
2. Locate the namespace that you want to delete in the list of namespaces.
3. On the far right side of the namespace listing, select Delete Namespace from the Options menu .
4. When the Delete Namespace pane opens, enter the name of the namespace that you want to delete in the field.
5. Click Delete.