Red Hat Ships OpenShift 5.0: What It Means for VM Workloads

Red Hat has released OpenShift Container Platform 5.0. The release notes say the release “is now available” (advisory RHEA-2026:4893) and runs Kubernetes 1.36 with the CRI-O runtime, and Red Hat’s product life cycle data lists 5.0 with a general availability date of November 3, 2026. OpenShift Virtualization Engine, the VM-only edition we track as a VMware alternative, runs on this platform, so 5.0 replaces 4.22 as the current version in our VMware alternatives tracker.

The support clock is the part that matters for planning. Red Hat’s life cycle data gives 5.0 full support through November 30, 2027, and maintenance support from December 1, 2027 to November 30, 2028. No Extended Update Support dates are listed for 5.0 yet. For 4.22, full support ends December 31, 2026, maintenance support ends December 31, 2027, and the optional EUS terms run to June 30, 2028 and June 30, 2029. Licensing for Virtualization Engine is unchanged in Red Hat’s subscription guide: one subscription per bare-metal node, regardless of sockets or cores.

Who this affects

Teams running or evaluating OpenShift Virtualization as a VMware exit, and anyone on 4.x who has to pick an update path. The 5.0 notes carry two VMware-specific items: OpenShift 5.0 is supported on VMware Cloud Foundation 9.1, and clusters on vSphere now support in-place vCenter upgrades from vCenter 8 to vCenter 9 without redeploying the cluster. See OpenShift Virtualization vs the field for how Red Hat compares with Nutanix, Hyper-V and Proxmox.

What to do now

  • Plan the node OS move. RHCOS in 5.0 uses RHEL 10.2 packages and new installs use RHCOS 10.2 by default. Red Hat says you can upgrade a cluster from 4.x to 5.0 and then update nodes to RHCOS 10.2, but a mix of RHCOS 9.x and 10.2 nodes is not supported, and downgrading from 10.2 to 9.x is not supported.
  • Switch to crun first. runC is deprecated in 5.0, and Red Hat says you cannot update the RHCOS version in a cluster that still uses the runC container runtime.
  • Check your ingress. 5.0 uses HAProxy 3.2.22 by default (4.22 used 2.8.18), which returns different HTTP errors for malformed requests. You can pin HAProxy 2.8 on an IngressController if you need to defer that change.
  • Staying on 4.22 is fine for now. Maintenance support runs to the end of 2027, and the EUS add-ons extend that to mid-2029. Our KVM vs VMware guide covers the operational differences before you move VMs.

Key details

ItemOpenShift 4.22OpenShift 5.0
General availabilityJune 9, 2026November 3, 2026
Full support endsDecember 31, 2026November 30, 2027
Maintenance support endsDecember 31, 2027November 30, 2028
Extended Update SupportTo June 30, 2028; Term 2 to June 30, 2029Not yet listed
Node OSRHCOS 9.xRHCOS 10.2 (RHEL 10.2 packages)
Default HAProxy2.8.183.2.22 (2.8.27 available)
Virtualization Engine licensingPer bare-metal nodePer bare-metal node (unchanged)

For the wider timeline behind VMware exits, see vSphere 8 support ends October 2027.

Source

Checked against Red Hat’s OpenShift 5.0 release notes and product life cycle data on November 5, 2026.