live wire
▸AI · EAGLE-4 0.1.4 fixes multi-GPU vLLM collective ordering during startupEAGLE-4▸SECURITY: Apache Camel 4.23.0, 4.22.2 and 4.18.5 fix eight component vulnerabilitiesApache Camel▸AI · Red Hat shows DRA doubles llm-d KV-cache throughput by aligning GPUs and RDMA NICsRed Hat Developer▸Red Hat Developer Hub 1.9.10 ships as a Critical security updateRed Hat errata▸OpenShift Dev Spaces 3.31 adds live editor switching and DevWorkspace Operator 1.0Red Hat documentation▸OpenShift Pipelines 1.24.1 tightens Manual Approval Gate RBAC and approval integrityRed Hat release notes▸AI · Red Hat survey: 97% of UK CIOs trust agent security, but 43% can trace data flowsRed Hat▸JAVA · IBM and Kaggle launch a living benchmark for agentic Java framework migrationsIBM Research▸AI · Red Hat tests policy-derived data controls for AI agentsRed Hat▸Apache Camel pattern turns routes into bounded LLM tools and MCP servicesRed Hat Developer▸Atos tunes small models on OpenShift AI for structured German-language analysisRed Hat Developer▸Red Hat publishes checklist for evaluating third-party OpenShift applicationsRed Hat Developer▸SECURITY · OpenShift 4.21.40 patches OpenSSL, OpenSSH and PCRE2 flawsRed Hat Product Security▸SECURITY · Apache Camel fixes A2A webhook SSRF gap in 4.22.2 and 4.23.0 (Oct. 23)Apache Camel▸AI · EAGLE-4 0.1.4 fixes multi-GPU vLLM collective ordering during startupEAGLE-4▸SECURITY: Apache Camel 4.23.0, 4.22.2 and 4.18.5 fix eight component vulnerabilitiesApache Camel▸AI · Red Hat shows DRA doubles llm-d KV-cache throughput by aligning GPUs and RDMA NICsRed Hat Developer▸Red Hat Developer Hub 1.9.10 ships as a Critical security updateRed Hat errata▸OpenShift Dev Spaces 3.31 adds live editor switching and DevWorkspace Operator 1.0Red Hat documentation▸OpenShift Pipelines 1.24.1 tightens Manual Approval Gate RBAC and approval integrityRed Hat release notes▸AI · Red Hat survey: 97% of UK CIOs trust agent security, but 43% can trace data flowsRed Hat▸JAVA · IBM and Kaggle launch a living benchmark for agentic Java framework migrationsIBM Research▸AI · Red Hat tests policy-derived data controls for AI agentsRed Hat▸Apache Camel pattern turns routes into bounded LLM tools and MCP servicesRed Hat Developer▸Atos tunes small models on OpenShift AI for structured German-language analysisRed Hat Developer▸Red Hat publishes checklist for evaluating third-party OpenShift applicationsRed Hat Developer▸SECURITY · OpenShift 4.21.40 patches OpenSSL, OpenSSH and PCRE2 flawsRed Hat Product Security▸SECURITY · Apache Camel fixes A2A webhook SSRF gap in 4.22.2 and 4.23.0 (Oct. 23)Apache Camel
upstreambeat.ai
releasePLATFORM

OpenShift 4.12’s final extended-support term ends January 14

Red Hat’s three-month notice gives remaining 4.12 operators a firm deadline to complete their move to a supported OpenShift release.

OpenShift support timeline ending at January 14 deadline.
Timeline: dates from the story
By The Release Desk· Oct 17, 2026the quick take — two AI hosts go live when you do

Red Hat has issued a three-month notice that Extended Update Support Term 3 for OpenShift Container Platform 4.12 ends January 14, 2027. The advisory was issued October 16 and applies to customers still operating OpenShift 4.12. Red Hat advisory RHBA-2026:83716

What changed

The advisory puts a date on the last optional extended-support term for the 4.12 stream. During Term 3, Red Hat says it supplied qualified Critical- and Important-impact security patches and selected mission-critical bug fixes. Software and documentation will remain available after the term ends, but the Term 3 support window itself will close on January 14. Red Hat advisory RHBA-2026:83716

Red Hat’s lifecycle policy describes Term 3 as an optional 12-month add-on after Term 2. Taken together, the three long-life add-on terms can extend an eligible OpenShift release to 48 months of support. For OpenShift 4.12 specifically, those add-on terms are available only on x86_64. OpenShift Container Platform life cycle policy

Who it affects

The deadline matters to organizations that still depend on OpenShift 4.12 and its Term 3 coverage for qualified security fixes, urgent fixes and technical support. It is not a new OpenShift release; it is a support-window change for an older EUS stream. Red Hat advisory RHBA-2026:83716

Layered products and Operators can follow lifecycles separate from the platform. Red Hat’s policy therefore directs customers to check the lifecycle and tested-configuration information for the content running on their clusters, rather than treating the platform deadline as the only dependency. OpenShift Container Platform life cycle policy

What to do

Teams still on 4.12 should identify affected clusters and subscriptions, select a supported destination release, validate the upgrade path and layered-product compatibility, and schedule the change before January 14. The remaining window is now measured in weeks rather than quarters; waiting until the term expires leaves upgrade assistance as the practical route back to a supported configuration. Red Hat advisory RHBA-2026:83716 OpenShift Container Platform life cycle policy

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