live wire
AI · Red Hat documents usage-based admission fair sharing for Kueue 1.4 on OpenShiftRed Hat DeveloperAI: Red Hat maps governed firewall changes from ServiceNow through Ansible and two human approval gatesRed Hat DeveloperCLUSTER MGMT · ACM 2.17 makes Submariner 0.24 GA with Important-rated fixesRed Hat ErrataPLATFORM · Red Hat makes on-premises Lightspeed recommendations GA for Satellite 6.18Red Hat ErrataSECURITY · Red Hat Hardened Images updates Tomcat 10 for nine authentication, access-control and DoS flawsRed Hat ErrataAI · Open Data Hub 3.6.0 EA1 bundles Trainer, MLflow and llm-d componentsOpen Data HubAI · Speculators 0.6.0 adds P-EAGLE parallel drafting for vLLM speculative decodingRed Hat DeveloperSECURITY · OpenShift 4.17.57 fixes seven Go and TLS CVEs in an Important-rated updateRed Hat ErrataAI · Red Hat benchmarks local LLM guardrails with EvalHub, exposing regex accuracy and latency trade-offsRed Hat DeveloperAI · Red Hat maps silent tool-call failures across agentic pipelinesRed HatAPI · Kuadrant 1.5.3 adds GRPCRoute policies and developer-portal API-key workflowsKuadrantAI · (Aug 25) IBM releases Apache-2.0 Granite 4.2 reasoning models in 3B, 8B and 30B sizesIBM ResearchJAVA · Red Hat build of Quarkus 3.33.3.SP1 fixes 13 CVEs in an Important-rated updateRed Hat errataAI · vLLM moves Kimi K2 RL weight sync across 384 H100s in 7.53 seconds (Aug 22)vLLMAI · Red Hat documents usage-based admission fair sharing for Kueue 1.4 on OpenShiftRed Hat DeveloperAI: Red Hat maps governed firewall changes from ServiceNow through Ansible and two human approval gatesRed Hat DeveloperCLUSTER MGMT · ACM 2.17 makes Submariner 0.24 GA with Important-rated fixesRed Hat ErrataPLATFORM · Red Hat makes on-premises Lightspeed recommendations GA for Satellite 6.18Red Hat ErrataSECURITY · Red Hat Hardened Images updates Tomcat 10 for nine authentication, access-control and DoS flawsRed Hat ErrataAI · Open Data Hub 3.6.0 EA1 bundles Trainer, MLflow and llm-d componentsOpen Data HubAI · Speculators 0.6.0 adds P-EAGLE parallel drafting for vLLM speculative decodingRed Hat DeveloperSECURITY · OpenShift 4.17.57 fixes seven Go and TLS CVEs in an Important-rated updateRed Hat ErrataAI · Red Hat benchmarks local LLM guardrails with EvalHub, exposing regex accuracy and latency trade-offsRed Hat DeveloperAI · Red Hat maps silent tool-call failures across agentic pipelinesRed HatAPI · Kuadrant 1.5.3 adds GRPCRoute policies and developer-portal API-key workflowsKuadrantAI · (Aug 25) IBM releases Apache-2.0 Granite 4.2 reasoning models in 3B, 8B and 30B sizesIBM ResearchJAVA · Red Hat build of Quarkus 3.33.3.SP1 fixes 13 CVEs in an Important-rated updateRed Hat errataAI · vLLM moves Kimi K2 RL weight sync across 384 H100s in 7.53 seconds (Aug 22)vLLM
upstreambeat.ai
newsPLATFORM

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.

OpenShift cluster versions 4.16 and 4.17 side by side.
AI-generated illustration
By The News Desk· Sep 1, 2026the quick take — two AI hosts, this story only

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.

Filed by The News Desk. Corrections: desk@upstreambeat.ai · Our standards →

comments · 0

    Comments are moderated before they appear. Your email is used once to confirm it is you — never shown, never sold. Corrections and questions get an answer from the desk when we have one.