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
releaseAPI

Red Hat deprecates Connectivity Link 1.4.0 and urges an update

The release notes warn that 1.4.0 can trigger authentication, API-key and gateway failures, while 1.4.3 closes policy-targeting and stability defects.

Deprecated version vs updated release, with failures on one side and fixes on the other.
Side by side: what changed
By The Release Desk· Sep 26, 2026the quick take — two AI hosts go live when you do

Red Hat has marked Connectivity Link 1.4.0 as deprecated and tells users to install or upgrade to version 1.4.1 or later. The warning is unusually direct for a z-stream update: the Connectivity Link 1.4 release notes say 1.4.0 can experience authentication failures, API-key management errors, gateway instability and gateway-pod memory pressure on some supported OpenShift and Service Mesh combinations.

What changed

The current release notes list 1.4.3, issued September 8, 2026, as the newest documented 1.4 update. Red Hat says it corrects three consequential defects: case-sensitive host matching that could bypass wasm-shim policy enforcement, overly broad policy targeting that could apply EnvoyFilter configuration to unrelated gateways, and an endless reconciliation loop that could exhaust the Kuadrant Operator's 300 MiB memory limit and cause intermittent HTTP 503 responses. The same release notes provide the advisory reference and the detailed fixes.

Connectivity Link 1.4 also changes the MCPServerRegistration API: the toolPrefix field is renamed to prefix. Red Hat says existing custom resources must be deleted and recreated rather than patched in place, so this is not a transparent schema-only change. The migration requirement is documented in the 1.4 notes.

Who it affects

The update matters to teams running Connectivity Link 1.4.0, particularly installations using authentication and API-key policies, multiple gateways in one namespace, or the MCP gateway. Administrators should also review manifests containing MCPServerRegistration resources before moving to the current 1.4 stream because the field rename requires resource recreation, according to the product documentation.

What to do

Red Hat's stated minimum action is to leave 1.4.0 and install or upgrade to 1.4.1 or later. For teams already planning that move, 1.4.3 is the latest update documented on the release-notes page and includes the policy-matching, gateway-targeting and reconciliation fixes described above. Operators should inventory MCPServerRegistration manifests, replace toolPrefix with prefix, and follow the documented delete-and-recreate migration path before applying those resources again.

sources

Filed by The Release 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