이 콘텐츠는 선택한 언어로 제공되지 않습니다.

Chapter 1. Red Hat Connectivity Link 1.2 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.0 as the Gateway API provider, which is based on the Istio community project.

1.1. New features and enhancements

  • New custom policy extensions:

    • OIDC policy: Low-code approach to authentication
    • Plan policy: Definition of usage plans for API consumers
    • Telemetry policy: More extensibility with metrics
  • Al gateway functionalities:

    • Token-based rate limiting policy: Control access to Al services by setting limits based on tokens
    • Token metrics: Evaluate the performance, efficiency, and resource consumption of Al models and applications
  • New builds of Connectivity Link for operation within ARM infrastructure
  • Seamless WASM plugin installation

1.2. Supported platforms and components

For details on all platform and component versions supported by Connectivity Link 1.2, see the following article:

1.4. Developer Preview features

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 provide early access to functionality in advance of possible inclusion in a Red Hat product offering. Customers can use these features to test functionality and provide 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 provide ways to submit feedback on Developer Preview features without an associated SLA. For more information, see Red Hat Developer Preview - Scope of Support.

Red Hat customers can provide feedback on Developer Preview features through your account teams. You can also ask questions and provide feedback directly by using the Connectivity Link contact form or by emailing rhcl-contactus@redhat.com.

1.4.1. Extension SDK

The Extension SDK is available in Connectivity Link as a Developer Preview feature.

The Extension SDK provides a framework for developers to build custom policy extensions that integrate with and extend Connectivity Link capabilities beyond core policies, such as AuthPolicy, RateLimitPolicy, TLSPolicy, and DNSPolicy.

Key features include:

  • Building custom policy controllers that follow Gateway API policy attachment patterns.
  • Integrating with the Connectivity Link control plane using gRPC over a Unix socket.
  • Using the Common Expression Language (CEL) for dynamic configuration evaluated against the Kuadrant context (topology, request data).
  • Publishing data bindings to share computed values or CEL programs with downstream components such as Authorino, Envoy WASM filters, or Limitador.
  • Subscribing to cluster events (Gateways, Routes, Policies) to react to changes.
  • Accessing helper functions to query the Kuadrant topology (Gateways, attached Policies) within CEL expressions.

Example extensions and a developer guide are available in the Kuadrant community repository to help users get started with building their own extensions. For more information, see Extension SDK.

1.6. Fixed issues

Expand
Table 1.1. Fixed issues in Connectivity Link 1.1.1
IssueDescription

CONNLINK-529

OpenShift Service Mesh pull secret configuration is cumbersome.

Previously, for RateLimitPolicy or AuthPolicy only, you were required to authenticate to registry.redhat.io to access the Wasm plug-in image used with OpenShift Service Mesh as the Gateway API provider. Now, authenticating to registry.redhat.io to access the Wasm plug-in image is no longer required.

CONNLINK-433

OpenShift 4.19 Gateway API compatibility.

Previously, on OpenShift 4.19, Connectivity Link used an incorrect Gateway API controller name. The Gateway API controller name is required in order to enable the Gateway API CRDs, which are now provided in OpenShift 4.19. Now, Connectivity Link uses the correct Gateway API controller name for OpenShift 4.19.

Expand
Table 1.2. Fixed issues in Connectivity Link 1.1.0
IssueDescription

CONNLINK-289

Namespace selector on Policies view switches user from sub-navigation item.

Previously, in the Policies view, in a specific policy list such as DNS policies, when you switched namespace, you returned to the All Policies view. Now, when you switch namespace, you stay in the original specific policy list.

1.7. Known issues

The following known issues apply in Connectivity Link 1.2:

CONNLINK-566 - Exploratory Testing of Dynamic Plugin

Some documentation links do not resolve or direct to the 1.1 version of Connectivity Link documentation instead of the 1.2 version.

CONNLINK-287 - Connectivity Link allows configuration for non-standard response codes

Connectivity Link should not allow configuration that specifies non-standard custom HTTP response codes such as HTTP 333.

Red Hat logoGithubredditYoutubeTwitter

자세한 정보

평가판, 구매 및 판매

커뮤니티

Red Hat 문서 정보

Red Hat을 사용하는 고객은 신뢰할 수 있는 콘텐츠가 포함된 제품과 서비스를 통해 혁신하고 목표를 달성할 수 있습니다. 최신 업데이트를 확인하세요.

보다 포괄적 수용을 위한 오픈 소스 용어 교체

Red Hat은 코드, 문서, 웹 속성에서 문제가 있는 언어를 교체하기 위해 최선을 다하고 있습니다. 자세한 내용은 다음을 참조하세요.Red Hat 블로그.

Red Hat 소개

Red Hat은 기업이 핵심 데이터 센터에서 네트워크 에지에 이르기까지 플랫폼과 환경 전반에서 더 쉽게 작업할 수 있도록 강화된 솔루션을 제공합니다.

Theme

© 2026 Red Hat
맨 위로 이동