Red Hat SummitChapter 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.
1.1. Connectivity Link new features
Support for the following new platform and component versions:
- OpenShift Container Platform 4.18
- Red Hat OpenShift Dedicated 4.18
- Red Hat OpenShift Service on AWS 4.18
- 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.2. Connectivity Link supported platforms and components
For details on all platform and component versions supported by Connectivity Link 1.1, see the following article:
1.3. Connectivity Link Developer Preview features
1.3.1. CoreDNS integration for on-prem DNS
Connectivity Link provides integration with CoreDNS for on-prem DNS as a Developer Preview feature. For more details, see the Kuadrant documentation on using CoreDNS.
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. Connectivity Link removed features
The following features have been removed from Connectivity Link 1.1:
1.4.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 Getting Started with API controller 1.0 Developer Preview.
1.5. Upgrading from Connectivity Link 1.0 to 1.1
You can upgrade from Connectivity Link 1.0.x to Connectivity Link 1.1.x by using the OperatorHub in the OpenShift web console.
1.5.1. Authenticating to registry.redhat.io for Wasm plug-in access
For RateLimitPolicy or AuthPolicy only, you must authenticate to registry.redhat.io to access the Wasm plug-in image used with OpenShift Service Mesh as the Gateway API provider.
Prerequisites
-
You have credentials to access
registry.redhat.io. If you do not have access, see Creating Registry Service Accounts.
Procedure
Create the following secret in your Gateway namespace:
oc create secret docker-registry wasm-plugin-pull-secret -n ${GATEWAY_NAMESPACE} \ --docker-server=registry.redhat.io \ --docker-username=your-registry-service-account-username \ --docker-password=your-registry-service-account-passwordoc create secret docker-registry wasm-plugin-pull-secret -n ${GATEWAY_NAMESPACE} \ --docker-server=registry.redhat.io \ --docker-username=your-registry-service-account-username \ --docker-password=your-registry-service-account-passwordCopy to Clipboard Copied! Toggle word wrap Toggle overflow - Repeat this step in each Gateway namespace in which a RateLimitPolicy or AuthPolicy is deployed.
1.5.2. Upgrading to Connectivity Link 1.1 in the web console
Prerequisites
- You already have Connectivity Link 1.0.x installed on OpenShift 4.17 or later.
- For RateLimitPolicy or AuthPolicy only, you have performed the steps in Section 1.5.1, “Authenticating to registry.redhat.io for Wasm plug-in access”.
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.1 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, see Updating installed Operators.
1.6. Connectivity Link resolved issues
| 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. Connectivity Link known issues
The following known issues apply in Connectivity Link 1.1:
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.
'%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}