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
newsPLATFORM

AAP 2.6 enters maintenance as 2.5 starts its final support year

The October lifecycle transition narrows the kinds of fixes Red Hat will accept and gives platform teams a dated migration boundary.

Support windows and compatibility differences for AAP 2.5 and 2.6.
AI-generated illustration
By The News Desk· Oct 5, 2026the quick take — two AI hosts go live when you do

Red Hat has moved Ansible Automation Platform 2.6 into Maintenance Support 1 and AAP 2.5 into Maintenance Support 2, turning an ordinary calendar transition into a planning deadline for automation teams.

The support window has narrowed

Red Hat’s AAP lifecycle policy now places 2.6 in Maintenance Support 1 from October 2, 2026 through October 1, 2027. The branch is scheduled for Maintenance Support 2 from October 2, 2027 through October 1, 2028.

AAP 2.5 has moved one step further, into Maintenance Support 2. Its published timeline runs only through 2027, making this the branch’s final scheduled support year.

The phase labels matter because the allowed change set contracts after Full Support. Red Hat’s table says Maintenance Support 1 provides Critical-only bug fixes alongside Critical and Important security fixes. Maintenance Support 2 is narrower still: customers should not expect new features, broad hardware enablement or routine enhancements on the aging branch.

What platform teams should decide now

Teams on 2.5 should treat the remaining window as migration time, not as another feature cycle. The practical question is whether to move first to 2.6 or plan directly around 2.7, based on the organization’s OpenShift and RHEL estate and the time needed to validate controllers, execution environments, private automation hub content and external integrations.

The current compatibility matrix gives that decision concrete boundaries. Red Hat lists AAP 2.6 with ansible-core 2.16, OpenShift 4.14 through 4.22, PostgreSQL 15 through 17, RPM installation on RHEL 9, and containerized installation on RHEL 9 or 10. AAP 2.5 is listed with ansible-core 2.16, OpenShift 4.12 through 4.20, PostgreSQL 15, RPM installation on RHEL 8 or 9, and containerized installation on RHEL 9 or 10.

That means a migration can intersect with database, OpenShift and host-operating-system changes rather than being a controller-only upgrade. Teams should inventory those dependencies while 2.5 is still supported and schedule testing before its final window closes.

The change is not an emergency, but it is a dated architectural constraint. Remaining on 2.5 trades migration work now for a shrinking remediation path; 2.6 buys more runway, but it too is already out of Full Support.

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