IBM Cloud Docs
RHEL deprecation for VPC clusters

RHEL deprecation for VPC clusters

Virtual Private Cloud only

Review the following information about the deprecation of Red Hat Enterprise Linux (RHEL) worker nodes for VPC clusters and the migration to Red Hat Enterprise Linux CoreOS (RHCOS) worker nodes.

The information on this page applies to VPC clusters only. It does not apply to Satellite or Classic clusters.

Beginning with version 4.18 clusters on VPC infrastructure, Red Hat Enterprise Linux (RHEL) worker nodes are deprecated. Support for RHEL worker nodes ends with the release of version 4.21. Migrate your clusters to use RHCOS worker nodes as soon as possible.

Red Hat Enterprise Linux CoreOS (RHCOS) is the default operating system and beginning with version 4.21, RHCOS is the only supported operated system for Red Hat OpenShift on IBM Cloud.

RHCOS represents the next generation of single-purpose container operating system technology by providing the quality standards of RHEL with automated, remote upgrade features.

Timeline

RHEL deprecation timeline
Stage Date Description
Announcement 4.18 release date: 23 May 2025 Beginning with cluster version 4.18, Red Hat Enterprise Linux CoreOS (RHCOS) is the default operating system and RHEL worker nodes are deprecated in this version. RHEL workers are still available in version 4.18 only to complete the migration to RHCOS workers.
Reminders Ongoing Periodic reminders will be sent to all users with deployments of RHEL worker nodes in their clusters informing them that the end of support date is coming with increasing frequency as the EOS date approaches.
End of support 4.21 release date date Cluster version 4.21 supports only RHCOS worker nodes. Migrate your RHEL 9 worker nodes to RHCOS before updating to version 4.21.

Migration steps

Review and complete the following steps for migration.

  1. Understand the timeline and plan for key milestone dates.
  2. Work with your CSM or TAM if one is assigned to your account.
  3. Complete the migration steps that apply to your use case.
  4. Verify your migration.