Questo contenuto non è disponibile nella lingua selezionata.

Chapter 1. Red Hat Connectivity Link 1.5 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.5 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, providing a control plane for you to configure and deploy ingress gateways and policies based on the Kubernetes Gateway API standard. Connectivity Link supports OpenShift Service Mesh 3.4 as the Gateway API provider, which is based on the Istio community project.

1.2. This release

Red Hat Connectivity Link 1.5, RHSA-2026:88203, is now available. This release includes the MCP gateway 1.0 as a Generally Available feature. New features, changes, and known issues that pertain to Connectivity Link 1.5 are included in this topic.

Full support ends with the release of the next minor version. Maintenance support ends with the minor version after that. See the Red Hat Connectivity Link Life Cycle Policy for details about version support and OpenShift Container Platform compatibility.

1.2.1. New features and enhancements

You can use the new features and enhancements that are available with Red Hat Connectivity Link 1.5.

Disconnected installation is now Generally Available
Installing Connectivity Link in a disconnected environment is now Generally Available. You can apply cloud-like traffic management within your private, secure network. For more information, see Install Connectivity Link in a disconnected environment.
Support for GRPCRoute policy attachment is Generally Available
With this Connectivity Link release, GRPCRoute policy attachment support is a Generally Available feature. You can attach AuthPolicy and RateLimitPolicy custom resources (CRs) to GRPCRoute CRs, enabling authentication and rate-limiting controls for gRPC services with native service and method matching. For more information, see GRPCRoute policy attachment support.
Support for IBM Power® and IBM® LinuxONE is Generally Available
With this release, you can install and run Connectivity Link on OpenShift Container Platform clusters that use the IBM Power® and IBM® LinuxONE, architecture. For more information, see Supported configurations.
Red Hat Developer Hub plugin is Generally Available
The Red Hat Developer Hub plugin for Connectivity Link is Generally Available. With a Red Hat Developer Hub subscription, you can create a self-service API catalog that makes API consumption easier and enables teams to work together more effectively. For more information, see Manage APIs through Red Hat Developer Hub.
Token-based rate limiting enhancements
TokenRateLimitPolicy now supports token usage extraction from OpenAI, Google Gemini, and AWS Bedrock response formats. You can configure JSON Pointers for other formats and reserve token capacity for requests in progress to help prevent concurrent requests from exceeding a limit. For more information, see Token-based rate limiting with TokenRateLimitPolicy.
MCP gateway: MCP gateway is now Generally Available
The MCP gateway is now Generally Available. Gather your Model Context Protocol (MCP) servers behind a single endpoint. Grow your agentic AI applications at scale without building in connectivity. Manage access to and the security of AI tools and MCP servers. For more information, see Introduction to the MCP gateway.
MCP gateway: MCP gateway adds new protocol support
With this release, the MCP gateway adds support for the 2026-07-28 stateless Model Context Protocol (MCP) protocol version. This enhancement means that MCP servers can operate like standard HTTP services in cloud-native environments. Every request is now self-describing and independent, meaning that you can scale your MCP servers while reducing costs. For more information, see Multi-protocol support for the MCP gateway.
MCP gateway: Audit trail documentation is updated
The MCP gateway documentation is updated with simplified configuration instructions for creating an audit trail. Use audit trails for compliance and accountability. Capture caller identity, tool names, and system status. For more information, see Audit MCP tool calls.
MCP gateway: NeMo Guardrails support
With this release, you can inspect tool call traffic in the MCP gateway with NeMo Guardrails. Configured guardrails can block unsafe tool calls and mask sensitive information. When guardrails are enabled, every tools call request is routed through the gateway and is checked against the guardrails path. For more information, see Enable guardrails on the MCP gateway.

1.2.2. Technology Preview features

You can try the Technology Preview features that are available with Red Hat Connectivity Link 1.5.

Important

Technology Preview features are not supported with Red Hat production service level agreements (SLAs). These features might not be functionally complete. Red Hat does not recommend using them in production.

Technology Preview features give you early access to upcoming product features. You can use these features to test new tools early and share your feedback. For more information, see Red Hat Technology Preview Features - Scope of Support.

Egress Gateway management

With this release of Connectivity Link, you can configure, secure, and monitor outbound traffic leaving your cluster as a Technology Preview feature. You must use OpenShift Service Mesh to use an egress gateway. With this enhancement, you can complete the following tasks:

  • Enforce request limits on egress traffic by to protect against third-party API quota exhaustion.
  • Verify internal workloads making outbound calls.
  • Securely fetch API credentials from external secret stores and inject them into outbound headers.
  • Gain visibility into outbound service health and network traffic by using metrics and access logs.

    For more information, see Set up outbound traffic from your cluster.

Extension SDK now available

With this update, extension SDK is available as a Technology Preview. You can build, package, and deploy custom policy extensions on your own release cadence without modifying core Connectivity Link Operator logic. Running as independent workloads, gRPC-based extensions dynamically adapt to cluster topology changes, such as Gateway object listeners, and shape per-request data plane behavior by using CEL expressions, HTTP request and response actions, and custom gRPC service callouts.

For more information, see Build and integrate custom policy extensions and Deploy custom policy extensions.

DNS failover with groups
With this release, DNS groups let you shift traffic to a standby cluster during a planned migration or outage as a Technology Preview. Update the active-groups TXT record to activate the standby group, and use Prometheus metrics to monitor group status and cleanup. For more information, see Configure DNS failover with groups.

1.2.3. Developer Preview features

You can try the Developer Preview features that are available with Red Hat Connectivity Link 1.5.

Important

Developer Preview features are not supported by Red Hat in any way and are not functionally complete or production-ready. Do not use Developer Preview features for production or business-critical workloads. Developer Preview features give you early access to functionality in advance of possible inclusion in a Red Hat product offering. Customers can use these features to test functionality and give feedback during the development process.

Developer Preview features might not have any documentation, are subject to change or removal at any time, and have received limited testing. Red Hat might give ways to submit feedback on Developer Preview features without an associated SLA. For more information, see Red Hat Developer Preview - Scope of Support.

MCP gateway in the OpenShift Container Platform web console
With this release, you can use the OpenShift Container Platform web console plugin to set up your MCP gateway installation and register Model Context Protocol (MCP) servers. The web console makes the system status of your MCP gateway and the servers it connects highly visible. For more information, see Use the OpenShift web console.

1.2.4. Fixed issues

See the included list for bugs that are fixed in Connectivity Link 1.5.

  • Before this release, generated EnvoyFilter resources did not preserve a deterministic order for rule matches and HTTP route match indices during controller updates. The Kuadrant Operator generated non-deterministic custom resource specifications on consecutive reconciliation cycles, causing the controller to detect false state changes and continuously re-apply EnvoyFilter updates to the API server. As a result, OpenShift Container Platform clusters had high CPU and memory consumption from reconciliation loops, excessive API server audit log churn, and unnecessary control-plane traffic. With this release, EnvoyFilter generation logic is updated to sort and preserve the order of rules and HTTP match indices deterministically. Operator CPU and API server load remain stable, eliminating background reconciliation churn and ensuring that EnvoyFilter custom resources are updated only when functional policy changes occur. (2184)

1.2.5. Known issues

Connectivity Link 1.5 has known issues. Use the following information to work around these issues.

  • 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. (CONNLINK-856)
  • If you use Connectivity Link on IBM Power® and IBM® LinuxONE in combination with OpenShift Service Mesh 3.4 and have a large amount of rate-limiting rules, these rules might fail. If case the rate-limiting feature does not work as expected, use a ValidatingAdmissionPolicy to override the generated Connectivity Link-generated WebAssembly EnvoyFilter. Configure an Envoy rate-limit to communicate directly with the Limitador component.

1.2.6. Asynchronous releases

Security, bug fix, and enhancement updates for Red Hat Connectivity Link 1.5 are released asynchronously through the Red Hat Network.

All Red Hat Connectivity Link 1.5 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 you enable notifications, 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.5. Versioned asynchronous releases, titled in the form Red Hat Connectivity Link 1.5.z, are detailed in the following subsections.

Red Hat logoGithubRedditYoutubeTwitter

Formazione

Prova, acquista e vendi

Community

Informazioni su Red Hat

Forniamo soluzioni consolidate che rendono più semplice per le aziende lavorare su piattaforme e ambienti diversi, dal datacenter centrale all'edge della rete.

Rendiamo l’open source più inclusivo

Red Hat si impegna a sostituire il linguaggio problematico nel codice, nella documentazione e nelle proprietà web. Per maggiori dettagli, visita il Blog di Red Hat.

Informazioni sulla documentazione di Red Hat

Legal Notice

Theme

© 2026 Red Hat
Torna in cima