live wire
▸PLATFORM · Quay.io push and pull operations hit intermittent 500 errors during maintenanceRed Hat status▸INTEGRATION · Apache Camel exposes incident and web search as parallel tools for a local agentApache Camel▸AI · Red Hat makes confidential GPU AI GA and previews VM-isolated Agent Sandbox (Aug. 4)Red Hat Blog▸SECURITY · Red Hat fixes Important MariaDB GIS memory-corruption flaw in Hardened ImagesRed Hat Product Security▸SECURITY · Red Hat restores CVE pages after a CWE dependency outage; monitoring continuesRed Hat status▸PLATFORM · Red Hat implements a fix for docs.redhat.com degradation and begins monitoringRed Hat status▸AI · vLLM combines PCP, DCP and host-memory offload to serve 1M-token GLM-5.3 contextsvLLM▸AI · vLLM ships day-zero MiniMax-M3.1-Flash support across NVIDIA and AMD GPUsvLLM▸SECURITY · Red Hat revokes compromised eMudhra certificates across RHEL and OpenShift trust storesRed Hat Product Security▸SECURITY · Red Hat rates PHP2Shell request-handling flaws Important; fixes are rolling outRed Hat Product Security▸AI · IBM maps GPU observability and FinOps controls across OpenShift clustersIBM Community▸IDENTITY · Red Hat shows Data Grid authentication through Keycloak 26 on OpenShiftRed Hat Developer▸AI · Red Hat layers tenant isolation, tool authorization and rate limits onto MCP gatewaysRed Hat Developer▸DATA · Red Hat maps direct LDAP and LDAPS authentication for Data Grid on OpenShiftRed Hat Developer▸PLATFORM · Quay.io push and pull operations hit intermittent 500 errors during maintenanceRed Hat status▸INTEGRATION · Apache Camel exposes incident and web search as parallel tools for a local agentApache Camel▸AI · Red Hat makes confidential GPU AI GA and previews VM-isolated Agent Sandbox (Aug. 4)Red Hat Blog▸SECURITY · Red Hat fixes Important MariaDB GIS memory-corruption flaw in Hardened ImagesRed Hat Product Security▸SECURITY · Red Hat restores CVE pages after a CWE dependency outage; monitoring continuesRed Hat status▸PLATFORM · Red Hat implements a fix for docs.redhat.com degradation and begins monitoringRed Hat status▸AI · vLLM combines PCP, DCP and host-memory offload to serve 1M-token GLM-5.3 contextsvLLM▸AI · vLLM ships day-zero MiniMax-M3.1-Flash support across NVIDIA and AMD GPUsvLLM▸SECURITY · Red Hat revokes compromised eMudhra certificates across RHEL and OpenShift trust storesRed Hat Product Security▸SECURITY · Red Hat rates PHP2Shell request-handling flaws Important; fixes are rolling outRed Hat Product Security▸AI · IBM maps GPU observability and FinOps controls across OpenShift clustersIBM Community▸IDENTITY · Red Hat shows Data Grid authentication through Keycloak 26 on OpenShiftRed Hat Developer▸AI · Red Hat layers tenant isolation, tool authorization and rate limits onto MCP gatewaysRed Hat Developer▸DATA · Red Hat maps direct LDAP and LDAPS authentication for Data Grid on OpenShiftRed Hat Developer
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