此内容没有您所选择的语言版本。

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 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. (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. (CONNLINK-856)
Red Hat logoGithubredditYoutubeTwitter

学习

尝试、购买和销售

社区

关于红帽文档

通过我们的产品和服务,以及可以信赖的内容,帮助红帽用户创新并实现他们的目标。 了解我们当前的更新.

让开源更具包容性

红帽致力于替换我们的代码、文档和 Web 属性中存在问题的语言。欲了解更多详情,请参阅红帽博客.

關於紅帽

我们提供强化的解决方案,使企业能够更轻松地跨平台和环境(从核心数据中心到网络边缘)工作。

Theme

© 2026 Red Hat
返回顶部