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

OpenShift 4.18 reaches its maintenance-support boundary

Clusters remaining on 4.18 need an applicable Extended Update Support add-on or an upgrade plan as standard maintenance ends Aug. 25.

OpenShift 4.18 support phases ending and extending over time.
Timeline: dates from the story
By The News Desk· Aug 25, 2026

Red Hat OpenShift Container Platform 4.18 reaches the end of its maintenance-support phase on Aug. 25, 2026. The lifecycle change does not remove the software or documentation, but it changes what operators can expect from Red Hat unless their subscription includes the applicable Extended Update Support coverage.

What changes

Red Hat’s OpenShift lifecycle table lists 4.18 maintenance support as running from Sept. 18, 2025, through Aug. 25, 2026. The first optional Extended Update Support Add-On term begins Aug. 26 and runs through Feb. 25, 2027; a second optional term is listed from Feb. 26, 2027, through Feb. 25, 2028.

During maintenance support, Red Hat says qualified Critical, Important and Moderate vulnerabilities with a CVSS score of 7.0 or higher are eligible for fixes, while urgent and selected high-priority bug fixes may also be released. After that phase, software and documentation remain available, but Red Hat says technical support is limited to assistance with upgrading to a supported version unless extended coverage applies.

Who is affected

The immediate decision belongs to platform teams still running standard OpenShift 4.18 subscriptions. Version 4.18 is an even-numbered EUS release, but continued coverage is not automatic for every subscription: Red Hat describes the first long-life EUS term as included with Premium subscriptions and available as an optional add-on for Standard subscriptions across OpenShift Container Platform and related OpenShift offerings.

The lifecycle page also warns that full cluster functionality can depend on Red Hat-hosted services whose availability is not guaranteed for unmaintained and unsupported OpenShift versions. Layered products and Operators have independent lifecycles, so keeping the base cluster covered does not by itself establish support for every installed component.

What operators should do

Teams staying on 4.18 should confirm that their entitlement includes the applicable EUS term before Aug. 26 and verify the separate lifecycle status of installed Operators and layered products. Teams without that coverage should plan an upgrade to a supported OpenShift minor rather than treating continued access to images and documentation as continued production support.

The practical boundary is straightforward: Aug. 25 is the last day of ordinary 4.18 maintenance support; Aug. 26 begins the optional extended-support path. Inventory, entitlement checks and an upgrade decision should be completed against that distinction.

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.