このコンテンツは選択した言語では利用できません。
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.3. Connectivity Link Technology Preview features リンクのコピーリンクがクリップボードにコピーされました!
Connectivity Link supports Red Hat OpenShift Service Mesh 3.0 as the required Gateway API provider. For more information, see the OpenShift Service Mesh documentation.
Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production.
Technology Preview features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process. For more information, see Red Hat Technology Preview Features - Scope of Support.
1.3.1. CoreDNS integration for on-prem DNS リンクのコピーリンクがクリップボードにコピーされました!
Connectivity Link provides integration with CoreDNS for on-prem DNS as a Technology Preview feature. For more details, see the Kuadrant documentation on using CoreDNS.
1.4. Developer Preview features リンクのコピーリンクがクリップボードにコピーされました!
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.5. Upgrading from Connectivity Link 1.1 to 1.2 リンクのコピーリンクがクリップボードにコピーされました!
You can upgrade from Connectivity Link 1.1.x to Connectivity Link 1.2.x by using the OperatorHub in the OpenShift web console.
On OpenShift 4.19 or later, if you are updating your cluster from a previous OpenShift version that contains Gateway API CRDs, you must ensure that these resources exactly match the Gateway API version supported by OpenShift 4.19. For more details, see the OpenShift documentation on managing Gateway API resources.
1.5.1. Upgrading to Connectivity Link 1.2 in the web console リンクのコピーリンクがクリップボードにコピーされました!
Prerequisites
- You already have Connectivity Link 1.1.x installed on OpenShift 4.17 or later.
Procedure
- Click Operators > Installed Operators > Red Hat Connectivity Link.
-
Ensure that the Update channel is set to
stable. -
If Update approval is set to Automatic, the upgrade will be approved and installed immediately when the Update channel is set to
stable. - If Update approval is set to Manual, click Install.
- Wait until the Connectivity Link Operator is deployed.
- Verify that Connectivity Link 1.2 is installed and that your deployment is up and running.
After upgrade
For RateLimitPolicy or AuthPolicy only, if you patched your subscription as a workaround for CONNLINK-299, enter the following command to ensure that your environment is set correctly:
oc patch subscription rhcl-operator -n openshift-operators --type=merge --patch '{"spec": {"config": {"env": null}}}'oc patch subscription rhcl-operator -n openshift-operators --type=merge --patch '{"spec": {"config": {"env": null}}}'Copy to Clipboard Copied! Toggle word wrap Toggle overflow
Additional resources
- For more information on Operators, see Updating installed Operators.
1.6. Fixed issues リンクのコピーリンクがクリップボードにコピーされました!
| Issue | Description |
|---|---|
| OpenShift Service Mesh pull secret configuration is cumbersome.
Previously, for RateLimitPolicy or AuthPolicy only, you were required to authenticate to | |
| 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. |
| Issue | Description |
|---|---|
| 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.