此内容没有您所选择的语言版本。
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)