What’s New

Red Hat Connectivity Link 1.3

What's new in Red Hat Connectivity Link

Red Hat OpenShift Documentation Team

Abstract

This guide provides the latest information on what's new in this release of Red Hat Connectivity Link.

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 Content from kuadrant.io is not included.Kuadrant community project. Connectivity Link provides a control plane for configuring and deploying ingress gateways and policies based on the Content from gateway-api.sigs.k8s.io is not included.Kubernetes Gateway API standard. Connectivity Link supports OpenShift Service Mesh 3.2 as the Gateway API provider, which is based on the Content from istio.io is not included.Istio community project.

See the This content is not included.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 Content from coredns.io is not included.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 Limitador custom resource (CR), both the initial limitador deployment and Operator update get stuck on a Multi-Attach error because of the persistent volume claim (PVC) volume. As a workaround, you can change the limitador deployment strategy to "Recreate" and the reconcilation process works as expected. (This content is not included.CONNLINK-855)
  • When either the Redis or RedisCached storage option is set in a Limitador CR and the limitador pod gets restarted for any reason, the first request to the gateway is never rate-limited. All http requests after this are rate-limited. (This content is not included.CONNLINK-856)

1.1.3. 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 This content is not included.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.

Red Hat Connectivity Link 1.3.1 bug fix and security update

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

  • Previously, the wasm-shim networking 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 the CheckResponse object now correctly replace existing values. This fix restores predictable header management. (Content from redhat.atlassian.net is not included.CONNLINK-867)
Red Hat Connectivity Link 1.3.2 bug fix and security update

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

  • Previously, the wasm-shim component processed protection policies, such as authentication or rate-limiting rules, out of sequence with the actual data forwarding. This created a race condition where the Gateway started 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 a Denied message. 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 definitive Allow decision. Denied requests are strictly terminated at the Gateway, ensuring the upstream server never sees unauthorized or throttled traffic. (Content from redhat.atlassian.net is not included.CONNLINK-912)

Legal Notice

Copyright © Red Hat.
Except as otherwise noted below, the text of and illustrations in this documentation are licensed by Red Hat under the Creative Commons Attribution–Share Alike 3.0 Unported license . If you distribute this document or an adaptation of it, you must provide the URL for the original version.
Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.
Red Hat, the Red Hat logo, JBoss, Hibernate, and RHCE are trademarks or registered trademarks of Red Hat, LLC. or its subsidiaries in the United States and other countries.
Linux® is the registered trademark of Linus Torvalds in the United States and other countries.
XFS is a trademark or registered trademark of Hewlett Packard Enterprise Development LP or its subsidiaries in the United States and other countries.
The OpenStack® Word Mark and OpenStack logo are trademarks or registered trademarks of the Linux Foundation, used under license.
All other trademarks are the property of their respective owners.