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
releasePLATFORM

Migration Toolkit for Virtualization 2.10 reaches end of life as 2.11 enters maintenance

Red Hat’s support table now leaves MTV 2.12 as the only release in full support, narrowing the supported upgrade path for OpenShift Virtualization migration teams.

MTV 2.10 and 2.12 support status compared at a glance.
Side by side: what changed
By The News Desk· Oct 7, 2026the quick take — two AI hosts go live when you do

Red Hat has moved two Migration Toolkit for Virtualization release lines across support boundaries: version 2.10 reached the end of its maintenance window on October 6, while version 2.11 entered maintenance support on October 7. The change leaves MTV 2.12 as the only listed release in full support, according to Red Hat’s product lifecycle table.

What changed

MTV 2.11, released February 23, 2026, completed full support on October 6 and is now in maintenance through February 1, 2027. Red Hat lists that release as compatible with OpenShift 4.19, 4.20 and 4.21.

MTV 2.10, released November 4, 2025, completed maintenance support on October 6. Its listed compatibility range is OpenShift 4.18 through 4.20, but the lifecycle table now places the release outside both full and maintenance support.

The current full-support line is MTV 2.12. Red Hat lists it for OpenShift 4.20, 4.21 and 4.22, with full support through February 1, 2027 and maintenance support through June 1, 2027.

What maintenance means

Red Hat’s policy draws a practical distinction between the two supported phases. During full support, qualified Critical and Important security advisories and selected high-priority bug fixes are released as available, with other fixes potentially arriving in periodic updates. During maintenance, Critical and Important security fixes continue, while urgent or selected high-priority bug fixes may be released; other fixes and enhancements are discretionary.

That makes the 2.11 transition more than a date on a table: teams can no longer expect the same breadth of fixes or enhancements they received during full support. For 2.10, the support window has closed altogether.

What platform teams should do

Operators still running MTV 2.10 should plan a move to a supported minor rather than treating its former OpenShift compatibility range as evidence of continuing product support. Red Hat says customers are expected to upgrade MTV to the most current supported minor version.

The target release depends on the OpenShift estate. MTV 2.11 remains supported for clusters on OpenShift 4.19, while MTV 2.12 starts at OpenShift 4.20. Teams on OpenShift 4.20 or 4.21 can choose the current full-support line; OpenShift 4.22 is listed only with MTV 2.12. Before scheduling migration work, platform teams should match the toolkit release to the destination cluster version and account for the shorter maintenance-only horizon on 2.11.

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