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
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