红帽全球峰会此内容没有您所选择的语言版本。
Chapter 1. Connectivity Link 1.3 release notes
Welcome to the Red Hat Connectivity Link release notes, where you can learn about what is new and what is fixed.
1.1. Red Hat Connectivity Link 1.3 release notes
Red Hat Connectivity Link is a modular and flexible solution for application connectivity, policy management, and API management in multicloud and hybrid cloud environments. You can use Connectivity Link to secure, protect, connect, and observe your APIs, applications, and infrastructure.
Connectivity Link is based on the Kuadrant community project. Connectivity Link provides a control plane for configuring and deploying ingress gateways and policies based on the Kubernetes Gateway API standard. Connectivity Link supports OpenShift Service Mesh 3.2 as the Gateway API provider, which is based on the Istio community project.
See the Red Hat Connectivity Link Life Cycle Policy for details about version support and OpenShift Container Platform compatibility.
1.1.1. New features and enhancements
You can use the new features and enhancements that are available with Red Hat Connectivity Link 1.3.
- CoreDNS integration for on-premise DNS is Generally Available
- Connectivity Link 1.3 provides integration with CoreDNS for on-premise DNS as a Generally Available feature.
For more information, see About using on-premise DNS with CoreDNS.
- Updated Observability documentation is now available
- Connectivity Link 1.3 includes enhanced Observability documentation, including configuring access logs, tracing, and request correlation. For more information, see Red Hat Connectivity Link observability.
1.1.2. Known issues
Connectivity Link 1.3 has two known issues.
-
When the disk storage option is enabled in the
Limitadorcustom resource (CR), both the initiallimitadordeployment and Operator update get stuck on aMulti-Attacherror because of the persistent volume claim (PVC) volume. As a workaround, you can change thelimitadordeployment strategy to"Recreate"and the reconcilation process works as expected. (CONNLINK-855) -
When either the
RedisorRedisCachedstorage option is set in aLimitadorCR and thelimitadorpod gets restarted for any reason, the first request to the gateway is never rate-limited. Allhttprequests after this are rate-limited. (CONNLINK-856)
1.2. Async releases
Security, bug fix, and enhancement updates for Red Hat Connectivity Link 1.3 are released asynchronously through the Red Hat Network. All Red Hat Connectivity Link 1.3 updates are available on the Red Hat Customer Portal. For more information about asynchronous updates, read the Red Hat Connectivity Link Life Cycle Policy.
Red Hat Customer Portal users can enable update notifications in the account settings for Red Hat Subscription Management (RHSM). When notifications are enabled, you are notified through email whenever new updates relevant to your registered systems are released.
This section is updated over time to provide notes on enhancements and bug fixes for future asynchronous releases of Red Hat Connectivity Link 1.3. Versioned asynchronous releases, for example with the Red Hat Connectivity Link 1.3.z, are detailed in the following subsections.
Issued: 30 April 2026
Red Hat Connectivity Link release 1.3.3 is now available. A description is available in the RHEA-2026:10743 advisory. Red Hat Connectivity Link uses the stable update channel to track and receive updates for the Red Hat Connectivity Link Operator. You can manage how your updates are applied through your Operator Lifecycle Manager (OLM) subscription resource. For more information, see Updating Red Hat Connectivity Link.
1.2.1.1. New features and enhancements
With this release, the Model Context Protocol (MCP) gateway is now available as a Technology Preview feature. This experimental feature is not intended for production use. The MCP gateway is available on the preview update channel. Note the following scope of support on the Red Hat Customer Portal for this feature: Technology Preview Features - Scope of Support.
The MCP gateway aggregates in-cluster and remote MCP servers behind a single endpoint. The MCP gateway discovers every tool available to you on registered MCP servers. You can achieve the following goals by using the MCP gateway:
- Focus on your agentic AI applications without building networking into your code by using the MCP gateway.
- Standardize access and security governance of MCP servers by setting policies that span clusters.
- Add and remove MCP servers without restarting your systems because the MCP gateway system state updates dynamically.
- Curate your MCP server tools by creating virtual MCP servers.
For more information, see Introduction to the MCP gateway
- With this release, elicitation support is available with the MCP gateway if your client supports them. MCP servers can implement interactive workflows by enabling user input requests. For more information, see the Elicitation documentation (MCP specification).
1.2.1.2. Known issues
When the default setting httpRouteManagement: Enabled is set on an MCPGatewayExtension custom resource, the MCP controller component buildGatewayHTTPRoute() only creates a single rule for /mcp endpoints. The /.well-known/oauth-protected-resource rule is missing.
The workaround is to set httpRouteManagement: Disabled in the MCPGatewayExtension CR in the config/mcp-gateway/ with a manually managed HTTPRoute CR.
See Applying a customized HTTPRoute object for instructions.
Issued: 8 April 2026
Red Hat Connectivity Link release 1.3.2 is now available. A description is available in the RHBA-2026:7016 advisory. Red Hat Connectivity Link uses the stable update channel to track and receive updates for the Red Hat Connectivity Link Operator. You can manage how your updates are applied through your Operator Lifecycle Manager (OLM) subscription resource. For more information, see Updating Red Hat Connectivity Link.
1.2.2.1. Bug fixes
-
Previously, the
wasm-shimcomponent processed protection policies, such as authentication or rate-limiting rules, out of sequence with the actual data forwarding. This created a race condition where theGatewaystarted sending the request to the upstream server at the same time it was asking the policy if the request was allowed. As a result, the upstream server had already received and potentially acted upon the request before the connection could be cut when the request was denied. Meanwhile, the downstream client correctly received aDeniedmessage. With this release, the logic is updated to ensure that the policy check is a blocking operation that must complete before any data is dispatched to the upstream backend. This fix synchronizes the state machine so that the connection to the upstream is only opened after the protection policy returns a definitiveAllowdecision. Denied requests are strictly terminated at the Gateway, ensuring the upstream server never sees unauthorized or throttled traffic. (CONNLINK-912)
Issued: 18 March 2026
Red Hat Connectivity Link release 1.3.1 is now available. A description is available in the RHBA-2026:4903 advisory. Red Hat Connectivity Link uses the stable update channel to track and receive updates for the Red Hat Connectivity Link Operator. You can manage how your updates are applied through your Operator Lifecycle Manager (OLM) subscription resource. For more information, see Updating Red Hat Connectivity Link.
1.2.3.1. Bug fixes
-
Previously, the
wasm-shimnetworking protcol incorrectly appended values to existing request headers instead of replacing them during the external authorization flow. This caused inconsistent behavior, leading to comma-separated header values that could disrupt upstream processing. With this release, the logic is updated to ensure that the headers provided in theCheckResponseobject now correctly replace existing values. This fix restores predictable header management. (CONNLINK-867)
'%20d='M201.5%20305.5c-13.8%200-24.9-11.1-24.9-24.6%200-13.8%2011.1-24.9%2024.9-24.9%2013.6%200%2024.6%2011.1%2024.6%2024.9%200%2013.6-11.1%2024.6-24.6%2024.6zM504%20256c0%20137-111%20248-248%20248S8%20393%208%20256%20119%208%20256%208s248%20111%20248%20248zm-132.3-41.2c-9.4%200-17.7%203.9-23.8%2010-22.4-15.5-52.6-25.5-86.1-26.6l17.4-78.3%2055.4%2012.5c0%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.3%2024.9-24.9s-11.1-24.9-24.9-24.9c-9.7%200-18%205.8-22.1%2013.8l-61.2-13.6c-3-.8-6.1%201.4-6.9%204.4l-19.1%2086.4c-33.2%201.4-63.1%2011.3-85.5%2026.8-6.1-6.4-14.7-10.2-24.1-10.2-34.9%200-46.3%2046.9-14.4%2062.8-1.1%205-1.7%2010.2-1.7%2015.5%200%2052.6%2059.2%2095.2%20132%2095.2%2073.1%200%20132.3-42.6%20132.3-95.2%200-5.3-.6-10.8-1.9-15.8%2031.3-16%2019.8-62.5-14.9-62.5zM302.8%20331c-18.2%2018.2-76.1%2017.9-93.6%200-2.2-2.2-6.1-2.2-8.3%200-2.5%202.5-2.5%206.4%200%208.6%2022.8%2022.8%2087.3%2022.8%20110.2%200%202.5-2.2%202.5-6.1%200-8.6-2.2-2.2-6.1-2.2-8.3%200zm7.7-75c-13.6%200-24.6%2011.1-24.6%2024.9%200%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.1%2024.9-24.6%200-13.8-11-24.9-24.9-24.9z'/%3e%3c/svg%3e){kind=small}