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
newsSECURITY

Red Hat Advanced Cluster Security 4.9 reaches its support boundary

RHACS 4.9 leaves maintenance support after August 31, putting upgrade planning on the critical path for clusters that remain on the release.

RHACS 4.9 support phases ending after August 31.
Timeline: dates from the story
By The News Desk· Aug 31, 2026the quick take — two AI hosts, this story only

Red Hat Advanced Cluster Security for Kubernetes 4.9 reaches the end of its maintenance-support window after August 31, 2026. Red Hat’s product lifecycle data lists 4.9 as supported through that date, while the company’s RHACS support policy says no technical support is provided after maintenance ends except help moving to a supported version.

What changes

RHACS 4.9 entered general availability on October 30, 2025. Its full-support phase ended April 30, 2026, and maintenance ran from May 1 through August 31, according to Red Hat’s lifecycle record. During maintenance, Red Hat says qualified Critical and Important security advisories may be delivered, along with urgent and selected high-priority bug fixes. New features and enhancements are not part of that phase.

Once the window closes, 4.9 moves outside that security and bug-fix commitment. The software and documentation remain available, but the published policy limits support to assistance upgrading to a maintained release.

Who is affected

The boundary matters to platform and security teams running RHACS 4.9 for workload scanning, policy enforcement and cluster security operations. It is a product-version boundary rather than an OpenShift end-of-life event: Red Hat describes RHACS as a platform-agnostic operator and publishes its lifecycle separately from OpenShift Container Platform.

Red Hat’s lifecycle data lists RHACS 4.10 and 4.11 in full support on August 31. The same record shows 4.10 compatible with OpenShift 4.12, 4.14 and 4.16 through 4.21, while 4.11 adds OpenShift 4.22 to its listed set and omits 4.17. Those matrices make the target release a compatibility decision, not simply a choice of the highest available version.

What teams should do

Operators should identify RHACS 4.9 installations, check their OpenShift version against Red Hat’s current compatibility data, and plan a move to a supported RHACS release. Red Hat’s policy also says customers are expected to run the most current micro release within a supported RHACS minor version to receive security and bug fixes.

The practical deadline is the support boundary itself: after August 31, remaining on 4.9 means operating without Red Hat’s normal maintenance-phase fix commitment. Upgrade validation should include Central, secured-cluster services and any policy or integration behavior that depends on the existing RHACS deployment.

sources

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.

    more from the desk