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

OpenShift 4.14 EUS Term 2 ends October 31

Red Hat’s two-month notice gives 4.14 operators until November to arrange the optional third support term or move to another supported OpenShift release.

OpenShift 4.14 support timeline ending in October and continuing with optional Term 3.
Timeline: dates from the story
By The Release Desk· Aug 31, 2026the quick take — two AI hosts, this story only

Red Hat has issued a two-month notice that OpenShift Container Platform 4.14 will leave Extended Update Support Term 2 on October 31, 2026. The advisory, RHBA-2026:61573, was published August 31.

What changed

Red Hat’s product lifecycle data places OpenShift 4.14 in Extended Update Support Term 2 from November 1, 2025 through October 31, 2026. Extended Update Support Term 3 begins November 1, 2026 and runs through October 31, 2027.

This is a support-phase boundary, not the end of every available support path for 4.14. Red Hat’s OpenShift lifecycle policy describes Term 3 as an optional 12-month add-on that follows Term 2. It includes technical support, qualifying Critical, Important and Moderate security backports, and urgent-priority bug fixes for the covered platform and selected aligned Operators.

Who it affects

The deadline matters to organizations that still run OpenShift 4.14 under the Term 2 add-on. Their current support term ends after October 31; continued coverage on that minor release depends on arranging the Term 3 add-on, according to Red Hat’s policy.

The policy also warns that layered products and Operators can have independent lifecycles. A cluster’s platform support date therefore does not establish support for every installed component.

What to do

OpenShift 4.14 operators should confirm their subscription entitlement and choose a supported path before November 1: obtain Term 3 coverage for 4.14 or schedule an update to another supported OpenShift release.

Before deciding to remain on 4.14, inventory Red Hat and third-party Operators and check each component’s lifecycle independently. Teams planning an update should also validate the supported upgrade path from their installed 4.14.z release rather than treating the support-phase deadline as an upgrade procedure.

sources

Filed by The Release 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.

    more from the desk