IBM Cloud Docs
Red Hat OpenShift on IBM Cloud version information

Red Hat OpenShift on IBM Cloud version information

Review information about the supported Red Hat OpenShift versions for Red Hat® OpenShift® on IBM Cloud® clusters.

View information of version changes for major, minor, and patch updates that are available for your Red Hat® OpenShift® on IBM Cloud® clusters. Changes include updates to Red Hat OpenShift, Kubernetes, and IBM Cloud Provider components.

Unless otherwise noted in the change logs, the IBM Cloud provider version enables Red Hat OpenShift APIs and features that are at beta. Red Hat OpenShift alpha features, which are subject to change, are disabled.

Check the Security Bulletins on IBM Cloud Status for security vulnerabilities that affect Red Hat OpenShift on IBM Cloud. You can filter the results to view only Kubernetes Service security bulletins that are relevant to Red Hat OpenShift on IBM Cloud. Change log entries that address other security vulnerabilities but don't also refer to an IBM security bulletin are for vulnerabilities that are not known to affect Red Hat OpenShift on IBM Cloud in normal usage. If you run privileged containers, run commands on the workers, or execute untrusted code, then you might be at risk.

Master patch updates are applied automatically. Worker node patch updates can be applied by reloading or updating the worker nodes. For more information about major, minor, and patch versions and preparation actions between minor versions, see Red Hat OpenShift versions.

For more details about the Red Hat OpenShift and Kubernetes project versions, review the Red Hat OpenShift release notes.

Available Red Hat OpenShift versions

Red Hat OpenShift on IBM Cloud supports the following versions of Red Hat OpenShift. Note that different Red Hat OpenShift versions might support different RHEL versions.

Red Hat Enterprise Linux CoreOS (RHCOS) worker nodes are available only for VPC clusters that were created at 4.15 and later. Clusters that are upgraded from 4.14 to 4.15 can't use RHCOS workers.

VPC clusters with CoreOS enabled

Latest Default 4.16 (Kubernetes 1.29)

4.15 (Kubernetes 1.28)

VPC and Classic clusters

Latest Default 4.16 (Kubernetes 1.29)

4.15 (Kubernetes 1.28)

4.14 (Kubernetes 1.27)

4.13 (Kubernetes 1.26)

Deprecated 4.12 (Kubernetes 1.25)

Clusters in Satellite locations with CoreOS enabled

Latest Default 4.16 (Kubernetes 1.29)

4.15 (Kubernetes 1.28)

4.14 (Kubernetes 1.27)

4.13 (Kubernetes 1.26)

Deprecated 4.12 (Kubernetes 1.25)

Clusters in Satellite locations without CoreOS enabled

Latest Default 4.16 (Kubernetes 1.29)

4.15 (Kubernetes 1.28)

4.14 (Kubernetes 1.27)

4.13 (Kubernetes 1.26)

Deprecated 4.12 (Kubernetes 1.25)

† Indicates dates that are tentative and subject to change.

Unsupported versions:
For information about unsupported versions, see the archive.

Release lifecycle

Each supported version of Red Hat OpenShift on IBM Cloud goes through a lifecycle of testing, development, general release, support, deprecation, and becoming unsupported. Review the descriptions of each phase of a version's lifecycle.

Estimated days and versions are provided for general understanding. Actual availability and release dates are subject to change and depend on various factors, such as community updates, security patches, and technology changes between versions.

  1. Community release: The community releases the new version. IBM engineers begin testing and hardening the community version in preparation to release a supported Red Hat OpenShift on IBM Cloud version.

  2. Supported version lifecycle:

    Development release
    Release is under development and might be available as a Beta to select customers. IBM provides best effort support for the release.
    General availability
    Release is generally available (GA). IBM provides full support for the release. IBM provides a tentative target date for the release to be unsupported. Release becomes the default version used during cluster creation once there are minimal restrictions and a reasonable adoption rate for the release.
    Maintenance
    Release has entered maintenance support as defined by Red Hat support. IBM provides maintenance support for OpenShift based on Red Hat policy. IBM provides full support otherwise.
    Extended support
    Release has entered extended support as defined by Red Hat. IBM provides extended support for OpenShift based on Red Hat policy. IBM provides full support otherwise.

  3. Deprecated version: The version is deprecated. IBM provides an updated unsupported target date for the release. An unsupported countdown to this date is provided at least 45 days before the release becomes unsupported. IBM provides minimal support for the release in alignment with Red Hat support. This support phase is generally the final phase before the release becomes unsupported and overrides the maintenance and extended support phases should there be any overlap. Security patch updates might not be provided. During the deprecation period, the version is still supported and your cluster is still functional, but might require updating to a supported release to fix security vulnerabilities. For example, by adding or reloading worker nodes.

  4. Unsupported version: The version is unsupported. IBM only provides support to upgrade to a supported release. The version is unsupported. Unsupported clusters are not provided with security and patch updates and are not supported by IBM Cloud Support. Although your cluster and apps might continue to run for a time, you can no longer create, reload, or take other corrective actions on your cluster master or worker nodes when an issue occurs. You can still delete the cluster or worker nodes, or update the cluster to the next version. Review the potential impacts and immediately update the cluster to continue receiving important security updates and support. If the cluster master runs two or more versions behind the oldest supported version, you can no longer apply updates and must delete the cluster and create a new one.

  5. Archived: The version is unsupported with no upgrade path. IBM provides no support. IBM reserves the right to shut down the control planes for such clusters.

IBM provides bi-weekly worker node fix packs. IBM's goal is to remediate detected, legitimate vulnerabilities within a timeframe appropriate for the risks they represent. To ensure the quality and stability of the release, fix packs might be delayed.

For Red Hat OpenShift, fix packs are applied to the latest minor release and patch for the targeted operating system.

  • For RHEL8 that is 8.9.

To keep your nodes secure, you must install worker node fix packs as soon as possible. You can subscribe to notifications to be alerted when a new update is available.

Archive

Unsupported clusters are not provided with security and patch updates and are not supported by IBM Cloud Support. Although your cluster and apps might continue to run for a time, you can no longer create, reload, or take other corrective actions on your cluster master or worker nodes when an issue occurs. You can still delete the cluster or worker nodes, or update the cluster to the next version. Review the potential impacts and immediately update the cluster to continue receiving important security updates and support. If your cluster master is two or more versions behind the oldest supported version, you must make a new cluster and deploy your apps to the new cluster.

Unsupported Red Hat OpenShift on IBM Cloud versions:
Archived version history