Learn about OpenShift Virtualization’s capabilities and support scope.
OpenShift Virtualization provides the scalable, enterprise-grade virtualization functionality in Red Hat OpenShift. You can use it to manage virtual machines (VMs) exclusively or alongside container workloads.
OpenShift Virtualization adds new objects into your Red Hat OpenShift Service on AWS cluster by using Kubernetes custom resources to enable virtualization tasks. These tasks include:
Creating and managing Linux and Windows VMs
Running pod and VM workloads alongside each other in a cluster
Connecting to VMs through a variety of consoles and CLI tools
Importing and cloning existing VMs
Managing network interface controllers and storage disks attached to VMs
Live migrating VMs between nodes
You can manage your cluster and virtualization resources by using the Virtualization perspective of the Red Hat OpenShift Service on AWS web console, and by using the OpenShift CLI (oc
).
You can use OpenShift Virtualization with OVN-Kubernetes.
You can check your OpenShift Virtualization cluster for compliance issues by installing the Compliance Operator and running a scan with the ocp4-moderate
and ocp4-moderate-node
profiles. The Compliance Operator uses OpenSCAP, a NIST-certified tool, to scan and enforce security policies.
If you are familiar with VMware vSphere, the following table lists OpenShift Virtualization components that you can use to accomplish similar tasks. However, because OpenShift Virtualization is conceptually different from vSphere, and much of its functionality comes from the underlying Red Hat OpenShift Service on AWS, OpenShift Virtualization does not have direct alternatives for all vSphere concepts or components.
vSphere concept | OpenShift Virtualization | Explanation |
---|---|---|
Datastore |
Persistent volume (PV) + |
Stores VM disks. A PV represents existing storage and is attached to a VM through a PVC. When created with the |
Dynamic Resource Scheduling (DRS) |
Pod eviction policy + |
Provides active resource balancing. A combination of pod eviction policies and a descheduler allows VMs to be live migrated to more appropriate nodes to keep node resource utilization manageable. |
NSX |
Multus + |
Provides an overlay network configuration. There is no direct equivalent for NSX in OpenShift Virtualization, but you can use the OVN-Kubernetes network provider or install certified third-party CNI plug-ins. |
Storage Policy Based Management (SPBM) |
Storage class |
Provides policy-based storage selection. Storage classes represent various storage types and describe storage capabilities, such as quality of service, backup policy, reclaim policy, and whether volume expansion is allowed. A PVC can request a specific storage class to satisfy application requirements. |
vCenter |
OpenShift Metrics and Monitoring |
Provides host and VM metrics. You can view metrics and monitor the overall health of the cluster and VMs by using the Red Hat OpenShift Service on AWS web console. |
vMotion |
Live migration |
Moves a running VM to another node without interruption. For live migration to be available, the PVC attached to the VM must have the |
vSwitch |
NMState Operator + |
Provides a physical network configuration. You can use the NMState Operator to apply state-driven network configuration and manage various network interface types, including Linux bridges and network bonds. With Multus, you can attach multiple network interfaces and connect VMs to external networks. |
OpenShift Virtualization 4.17 is supported for use on Red Hat OpenShift Service on AWS clusters. To use the latest z-stream release of OpenShift Virtualization, you must first upgrade to the latest version of Red Hat OpenShift Service on AWS.
If you use the storage API with known storage providers, the volume and access modes are selected automatically. However, if you use a storage class that does not have a storage profile, you must configure the volume and access mode.
For best results, use the ReadWriteMany
(RWX) access mode and the Block
volume mode. This is important for the following reasons:
ReadWriteMany
(RWX) access mode is required for live migration.
The Block
volume mode performs significantly better than the Filesystem
volume mode. This is because the Filesystem
volume mode uses more storage layers, including a file system layer and a disk image file. These layers are not necessary for VM disk storage.
You cannot live migrate virtual machines with the following configurations:
Set the |