Support Policies for RHEL High Availability Clusters - Red Hat OpenShift Virtualization Virtual Machines as Cluster Members
Contents
Overview
Applicable Environments
- Red Hat Enterprise Linux (RHEL) with the High Availability Add-On
- Red Hat OpenShift Virtualization to provide Virtual Machines that may serve as High Availability cluster members
Recommended Prior Reading
- General conditions with virtualized cluster members
- This content is not included.Virtualization with Red Hat OpenShift
Useful References and Guides
Introduction
This guide offers Red Hat's policies, requirements, and limitations applicable to the use of Red Hat OpenShift Virtualization Virtual Machines as members of a RHEL High Availability cluster. Users of RHEL High Availability software components should adhere to these policies by installing only on the approved platforms in order to be eligible to receive assistance from Red Hat Support with the appropriate support subscriptions.
Policies
Red Hat OpenShift Virtualization Virtual Machines as RHEL High Availability members: Red Hat only supports Red Hat OpenShift Virtualization Virtual Machines as RHEL High Availability members on the following version or when a particular package version is installed.
- Red Hat OpenShift Virtualization 4.9 or later.
- Virtual Machines: RHEL 8.4.z or later and RHEL 9.0 or later.
Virtual Machine Architectures: Only support x86_64.
Cluster-shared-storage configurations that are supported: When utilizing shared storage for any managed use-case within the High Availability cluster, Red Hat expects that the following storage configurations should be compatible with clustering use-cases:
- Shared storage that is presented by Red Hat OpenShift Virtualization through the hypervisor that provides a consistent view of the shared storage across all virtual machines that are cluster nodes.
- iSCSI or network LUNs initiated/accessed directly by virtual machines without any pass-through of the Red Hat OpenShift Virtualization layers.
Cluster-shared-storage configurations that are not supported: These use-cases are not supported.
- Resilient Storage (ex. shared or clustered LVM,
lvmlockd,clvm, gfs2, etc) is not supported.
Available fence methods:
fence_kubevirtfence_sbdis not supported.fence_scsiandfence_mpathis not supported.