Red Hat SummitQuesto contenuto non è disponibile nella lingua selezionata.
Chapter 1. Connectivity Link 1.1 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.1 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.
See the Red Hat Connectivity LInk Life Cycle Policy for details about version support and OpenShift Container Platform compatibility.
1.2. New features and enhancements
You can use the new features and enhancements that are available with Red Hat Connectivity Link 1.1.
Support for the following new platform and component versions:
- OpenShift Container Platform 4.20, 4.18
- Red Hat OpenShift Dedicated 4.20, 4.18
- Red Hat OpenShift Service on AWS 4.20, 4.18
- Microsoft Azure Red Hat OpenShift 4.17
- cert-manager for Red Hat OpenShift 1.15
- Red Hat build of Keycloak 26.2
- Improved configuration for enabling Connectivity Link observability. For more information, see the Connectivity Link Observability Guide.
- Observability metrics displayed in OpenShift console dynamic plug-in. For details on enabling the dynamic plug-in, see Installing Connectivity Link on OpenShift.
1.3. Developer Preview features
Developer Preview features are included in Connectivity Link 1.1.
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 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 give feedback on Developer Preview features through your account teams. You can also ask questions and give feedback directly by using the Connectivity Link contact form or by emailing rhcl-contactus@redhat.com.
1.3.1. CoreDNS integration for on-premise DNS
Connectivity Link provides integration with CoreDNS for on-premise DNS as a Developer Preview feature. For more information, see the Kuadrant documentation on using CoreDNS.
1.4. Removed features
The following features have been removed from Connectivity Link 1.1:
- API controller 1.0 Developer Preview
API controller 1.0 Developer Preview was based on the Apicurio community project and included the following components:
- API designer based on Apicurio Studio
- API catalog based on Apicurio Registry
For more information, see {LinkRHCLAPIController}[{NameRHCLAPIController}].
1.5. Fixed issues
See the included list for bugs that are fixed in Connectivity Link 1.1.
1.5.1. Fixed issues in Connectivity Link 1.1.1
-
Previously, for
RateLimitPolicyorAuthPolicyonly, you were required to authenticate toregistry.redhat.ioto access the WASM plugin image used with OpenShift Service Mesh as the Gateway API provider. Authenticating toregistry.redhat.ioto access the WASM plugin image is no longer required. (CONNLINK-529) - Previously, on OpenShift Container Platform 4.19, Connectivity Link used an incorrect Gateway API controller name. The Gateway API controller name is required to enable the Gateway API Custom Resource Definitions (CRDs). Now, Connectivity Link uses the correct Gateway API controller name for OpenShift Container Platform 4.19. (CONNLINK-433)
1.5.2. Fixed issues in Connectivity Link 1.1.0
- 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. (CONNLINK-289)
1.6. Known issues
Listed are the known issues that apply in Connectivity Link 1.1.
- 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 (CONNLINK-287).
'%20d='M201.5%20305.5c-13.8%200-24.9-11.1-24.9-24.6%200-13.8%2011.1-24.9%2024.9-24.9%2013.6%200%2024.6%2011.1%2024.6%2024.9%200%2013.6-11.1%2024.6-24.6%2024.6zM504%20256c0%20137-111%20248-248%20248S8%20393%208%20256%20119%208%20256%208s248%20111%20248%20248zm-132.3-41.2c-9.4%200-17.7%203.9-23.8%2010-22.4-15.5-52.6-25.5-86.1-26.6l17.4-78.3%2055.4%2012.5c0%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.3%2024.9-24.9s-11.1-24.9-24.9-24.9c-9.7%200-18%205.8-22.1%2013.8l-61.2-13.6c-3-.8-6.1%201.4-6.9%204.4l-19.1%2086.4c-33.2%201.4-63.1%2011.3-85.5%2026.8-6.1-6.4-14.7-10.2-24.1-10.2-34.9%200-46.3%2046.9-14.4%2062.8-1.1%205-1.7%2010.2-1.7%2015.5%200%2052.6%2059.2%2095.2%20132%2095.2%2073.1%200%20132.3-42.6%20132.3-95.2%200-5.3-.6-10.8-1.9-15.8%2031.3-16%2019.8-62.5-14.9-62.5zM302.8%20331c-18.2%2018.2-76.1%2017.9-93.6%200-2.2-2.2-6.1-2.2-8.3%200-2.5%202.5-2.5%206.4%200%208.6%2022.8%2022.8%2087.3%2022.8%20110.2%200%202.5-2.2%202.5-6.1%200-8.6-2.2-2.2-6.1-2.2-8.3%200zm7.7-75c-13.6%200-24.6%2011.1-24.6%2024.9%200%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.1%2024.9-24.6%200-13.8-11-24.9-24.9-24.9z'/%3e%3c/svg%3e){kind=small}