A Red Hat OpenShift cluster with OpenShift Virtualization installed and configured. For installation instructions, see the documentation here.

Two NetApp ONTAP storage systems with an SVM configured on each, to provide storage for the active and the disaster recovery OpenShift clusters. Each SVM must have at least one management LIF and one data LIF configured and accessible from the corresponding OpenShift cluster.

Cluster peering and SVM peering configured between the two ONTAP systems to allow replication of data from the source cluster's SVM to the target cluster's SVM. For instructions on how to set up cluster peering and SVM peering, see the ONTAP cluster peering documentation here.

NetApp Trident installed and configured on the OpenShift cluster to provision persistent storage from the ONTAP SVM. For installation instructions, see the Trident documentation here.

Trident backend configuration created for the ONTAP SVM and a StorageClass configured on the OpenShift cluster to use that Trident backend as the provisioner. For instructions on how to create a Trident backend configuration and StorageClass, see the Trident backend configuration documentation here.

Cluster-admin access to the OpenShift cluster and admin access to the ONTAP storage system to perform the necessary configurations.

An admin workstation with tridentctl and oc tools installed and added to the $PATH environment variable to interact with the OpenShift cluster and Trident.

Adequate hardware resources on the OpenShift cluster to support the OpenShift Virtualization operator and the VMs that will be provisioned. For more details on resource requirements, see the documentation here.

Optionally, configure node placement rules for OpenShift Virtualization to specify a subset of cluster nodes to host the OpenShift Virtualization operators, controllers, and VMs. For instructions on how to configure node placement rules, see the documentation here.

For the storage backing OpenShift Virtualization, it is recommended to have a dedicated StorageClass that requests storage from a particular Trident backend, which in turn is backed by a dedicated SVM. This maintains a level of multitenancy with regard to the data being served for VM-based workloads on the OpenShift cluster.

A VM must be available in OpenShift Virtualization. For details about deploying a new VM, or migrating an existing VM into OpenShift Virtualization, see the appropriate section in the documentation.