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
newsAUTOMATION

Red Hat puts Ansible MCP servers on a separate 12-month support clock

The policy gives each GA build eight months of full support, four months of maintenance, and a version date that operators can use to calculate end of life.

Red Hat Ansible MCP servers on a separate 12-month support clock
Timeline: dates from the story
By The News Desk· Oct 2, 2026the quick take — two AI hosts go live when you do

Red Hat has defined a separate support lifecycle for the Model Context Protocol servers it ships with Ansible Automation Platform. The new policy gives each MCP server GA release a 12-month window, rather than tying its support dates directly to the longer lifecycle of the underlying AAP release.

What changed

Each Red Hat-shipped Ansible MCP server release now receives eight months of full support followed by four months of maintenance support. During full support, Red Hat says it will address Critical, Important and Moderate security issues with CVSS scores of 7.0 or higher, fix bugs at all severities and may deliver selected enhancements. During months nine through 12, coverage narrows to Critical and Important security issues and Critical bug fixes, with no new features. The release reaches end of life after month 12.

The lifecycle runs independently of the AAP platform lifecycle. That means one AAP minor can carry multiple MCP server releases with overlapping support windows, and the MCP component can age out while the associated AAP release remains supported.

How operators identify the window

Red Hat uses a date-bearing version format: {AAP_VERSION}.{YYYYMMDD}[.{patch}]. A build such as 2.6.20260315 was built and tested for AAP 2.6 and began its lifecycle on March 15, 2026; an additional suffix denotes an in-window patch revision.

The policy says an MCP server is supported only against the AAP minor in its version prefix. Customers must keep deployments on the latest or previous GA MCP server release to remain in the supported window. Platform teams therefore need to inventory the MCP server image or RPM separately from AAP itself and calculate support dates from the embedded version date.

What the subscription covers

Coverage is included with an active AAP subscription for Red Hat-shipped MCP servers that authenticate through the AAP Gateway API. Red Hat says customer-developed and third-party MCP servers receive only commercially reasonable support. LLM provider integrations and the behavior of connected models are outside the support scope.

For teams introducing AI assistants into automation workflows, the practical change is a second upgrade cadence: keeping AAP supported is not enough on its own. MCP server versions need their own lifecycle checks, compatibility validation against the AAP minor, and replacement planning before the 12-month boundary.

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