IBM Cloud ends support for OpenShift 4.16 clusters
IBM says Red Hat OpenShift on IBM Cloud 4.16 became unsupported on August 26 and tells operators to move to version 4.17 or later.
IBM says Red Hat OpenShift on IBM Cloud version 4.16 became unsupported on August 26, 2026, and tells customers to update affected clusters to version 4.17 or later as soon as possible.
The notice appears in IBM Cloud’s Red Hat OpenShift on IBM Cloud release notes, which were last updated August 31. IBM gives no additional qualification in the August 26 entry: it identifies 4.16 as unsupported and names 4.17 as the minimum target version.
What changed
IBM’s August 26 release-note entry establishes a completed support transition rather than announcing a future deadline. The entry states that Red Hat OpenShift on IBM Cloud 4.16 “is no longer supported” and repeats that the version is unsupported as of that date.
The same entry supplies the required next step in one sentence: update the cluster to at least version 4.17 as soon as possible. It does not identify a later grace date or describe a separate post-August 26 support phase.
IBM added other entries to the page after the lifecycle notice. The August 31 items concern patch updates for the OpenShift Virtualization cluster add-on and IBM Cloud Image Key Synchronizer. Those entries are separate from the August 26 notice and do not revise its stated minimum target of OpenShift 4.17.
Who is affected
The notice applies to Red Hat OpenShift on IBM Cloud clusters that remain on version 4.16. It does not say that every IBM Cloud OpenShift cluster must move immediately; its instruction is tied to the version that crossed the support boundary.
For teams tracking managed OpenShift versions, the operative facts in IBM’s notice are narrow: 4.16 is unsupported from August 26, and 4.17 is the minimum version IBM names for the update.
What to do
IBM’s published direction is to update affected clusters to OpenShift 4.17 or later as soon as possible. The release note does not prescribe a particular update sequence, testing plan or rollback procedure, so this desk does not infer one.
Operators should use IBM Cloud’s product documentation for the actual update procedure and treat the August 26 entry as the source for the support date and minimum destination version. The key deadline has already passed: any Red Hat OpenShift on IBM Cloud cluster still on 4.16 is now on a version IBM labels unsupported.
sources
- Red Hat OpenShift on IBM Cloud release notescloud.ibm.com
comments · 0