OpenShift docs are moving and will soon only be available at docs.redhat.com, the home of all Red Hat product documentation. Explore the new docs experience today.
  1. Documentation
    2. history
×

Upgrading container-native virtualization

You enable automatic updates during container-native virtualization installation. Learn what to expect and how you can check the status of an update in progress.

Container-native virtualization is a Technology Preview feature only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process.

For more information about the support scope of Red Hat Technology Preview features, see https://access.redhat.com/support/offerings/techpreview/.

About upgrading container-native virtualization

If you enabled automatic updates when you installed container-native virtualization, you receive updates as they become available.

Additional information

  • In container-native virtualization version 2.1, only z-stream updates are available. For example, container-native virtualization 2.1.0 → container-native virtualization 2.1.1

  • Updates are delivered via the Marketplace Operator, which is deployed during OpenShift Container Platform installation. The Marketplace Operator makes external Operators available to your cluster.

  • Upgrading does not interrupt virtual machine workloads.

    • Virtual machine Pods are not restarted or migrated during an upgrade. If you need to update the virt-launcher Pod, you must restart or live migrate the virtual machine.

      Each virtual machine has a virt-launcher Pod that runs the virtual machine instance. The virt-launcher Pod runs an instance of libvirt, which is used to manage the virtual machine process.

  • Upgrading does not interrupt network connections.

  • DataVolumes and their associated PersistentVolumeClaims are preserved during upgrade.

  • The amount of time an update takes to complete depends on your network connection. Most automatic updates complete within fifteen minutes.

Monitoring upgrade status

The best way to monitor container-native virtualization upgrade status is to watch the ClusterServiceVersion (CSV) PHASE. You can also monitor the CSV conditions in the web console or by running the command provided here.

The PHASE and conditions values are approximations that are based on available information.
Prerequisites

  • Access to the cluster as a user with the cluster-admin role.

  • Install the OpenShift Command-line Interface (CLI), commonly known as oc.

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
Additional information