live wire
▸JAVA · Quarkus 4.0.0.Beta1 moves to Java 21, adds HTTP/3 and starts extension migration (Oct. 1)Quarkus▸SECURITY · X41 shows shared /dev/shm can turn Envoy hot restart into cross-container lateral movementX41 D-Sec▸DATA · AWS and Red Hat map Confluent Platform on ROSA with HCP, CFK and OpenShift security controlsAWS IBM & Red Hat▸API · Red Hat resolves intermittent 3scale API Manager latencyRed Hat Status▸AI · IBM shows Maximo workflows exposed as approval-gated MCP tools on OpenShiftIBM Community▸AI · vLLM adds day-zero NVIDIA Vera Rubin support and reports 7.8× per-GPU throughputvLLM▸INTEGRATION · Apache Camel 4.23 makes Kamelets visible to AI tooling and validationApache Camel▸SECURITY · OpenShift 4.14.75 fixes five CVEs, including two SQLite code-execution flawsRed Hat Customer Portal▸SUPPLY CHAIN · Red Hat maps CRA-ready open source practices as EU reporting rules take effectRed Hat Blog▸AI · Red Hat AI Inference on IBM Cloud adds an OpenAI-compatible Embeddings APIIBM Cloud▸API · Red Hat investigates degraded 3scale API Management SaaS APIsRed Hat Status▸PLATFORM · Red Hat and Cloudera validate a 100-VM analytics stack on OpenShift VirtualizationRed Hat Blog▸DEVELOPER HUB · Red Hat maps a four-zone, quota-aware Dev Spaces architectureRed Hat Developer▸INTEGRATION · Camel 4.23 teaches agent tools to discover and validate KameletsApache Camel▸JAVA · Quarkus 4.0.0.Beta1 moves to Java 21, adds HTTP/3 and starts extension migration (Oct. 1)Quarkus▸SECURITY · X41 shows shared /dev/shm can turn Envoy hot restart into cross-container lateral movementX41 D-Sec▸DATA · AWS and Red Hat map Confluent Platform on ROSA with HCP, CFK and OpenShift security controlsAWS IBM & Red Hat▸API · Red Hat resolves intermittent 3scale API Manager latencyRed Hat Status▸AI · IBM shows Maximo workflows exposed as approval-gated MCP tools on OpenShiftIBM Community▸AI · vLLM adds day-zero NVIDIA Vera Rubin support and reports 7.8× per-GPU throughputvLLM▸INTEGRATION · Apache Camel 4.23 makes Kamelets visible to AI tooling and validationApache Camel▸SECURITY · OpenShift 4.14.75 fixes five CVEs, including two SQLite code-execution flawsRed Hat Customer Portal▸SUPPLY CHAIN · Red Hat maps CRA-ready open source practices as EU reporting rules take effectRed Hat Blog▸AI · Red Hat AI Inference on IBM Cloud adds an OpenAI-compatible Embeddings APIIBM Cloud▸API · Red Hat investigates degraded 3scale API Management SaaS APIsRed Hat Status▸PLATFORM · Red Hat and Cloudera validate a 100-VM analytics stack on OpenShift VirtualizationRed Hat Blog▸DEVELOPER HUB · Red Hat maps a four-zone, quota-aware Dev Spaces architectureRed Hat Developer▸INTEGRATION · Camel 4.23 teaches agent tools to discover and validate KameletsApache 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