Before you install OpenShift Virtualization, ensure that your OpenShift Container Platform cluster meets the following requirements:

In OpenShift Virtualization clusters installed using installer-provisioned infrastructure and with MachineHealthCheck properly configured, if a node fails the MachineHealthCheck and becomes unavailable to the cluster, it is recycled. What happens next with VMs that ran on the failed node depends on a series of conditions. See About RunStrategies for virtual machines for more detailed information about the potential outcomes and how RunStrategies affect those outcomes.

  • Shared storage is required to enable live migration.

  • You must manage your Compute nodes according to the number and size of the virtual machines that you want to host in the cluster.

  • To deploy OpenShift Virtualization in a disconnected environment, you must configure Operator Lifecycle Manager on restricted networks.

  • When using a disconnected cluster on a restricted network, you must configure proxy support in Operator Lifecycle Manager to access the Red Hat-provided OperatorHub. Using a proxy allows the cluster to fetch the OpenShift Virtualization Operator.

  • If your cluster uses worker nodes from multiple CPU vendors, live migration failures can occur. For example, a virtual machine with an AMD CPU might attempt to live-migrate to a node with an Intel CPU and likely fail migration. To avoid this, label nodes with a vendor-specific label, such as Vendor=Intel or Vendor=AMD, and set node affinity on your virtual machines to ensure successful migration. See Configuring a required node affinity rule for more information.

OpenShift Virtualization works with OpenShift Container Platform by default, but the following installation configurations are recommended:

To obtain an evaluation version of OpenShift Container Platform, download a trial from the OpenShift Container Platform home page.