Red Hat SummitChapter 1. Red Hat Connectivity Link 1.0 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. Connectivity Link enables you to secure, protect, connect, and observe your APIs, applications, and infrastructure.
The cloud application connectivity and policy management features provided by Connectivity Link are based on the Kuadrant community project. The API management features include the API controller 1.0 Developer Preview with an API editor and API registry based on the Apicurio 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 Red Hat OpenShift Service Mesh 3.0 as the Gateway API provider, which is based on the Istio community project.
1.1. Connectivity Link new features
1.1.1. Application connectivity
Connectivity Link provides the following application connectivity management features for platform engineers:
- DNS routing and global load balancing
DNS policy management
- Simple and advanced DNS strategies
- Endpoint health checks
TLS policy management
- ACME integration
- Automatic certificate generation for Gateways
Integration with cloud service providers
- Amazon Web Services
- Google Cloud Platform
- MicroSoft Azure
- Integration with OpenShift and other Red Hat products
1.1.2. API management
Connectivity Link provides the following API management features for application developers and business users:
- Composable API management
- API designer based on Apicurio Studio
- API catalog based on Apicurio Registry
- Integration with Prometheus and Grafana for monitoring
- API lifecycle management
- Rate limiting policies
- Authentication and authorization policies
1.2. Connectivity Link supported platforms and components
For details on the platform and component versions supported by Red Hat Connectivity Link 1.0, see the following article:
Connectivity Link supports OpenShift Service Mesh 3.0 General Availability as the required Gateway API provider. Upgrading from OpenShift Service Mesh 3.0 Technology Preview is not supported. You must install OpenShift Service Mesh 3.0 GA. For more information, see the OpenShift Service Mesh 3.0 documentation.
1.3. Connectivity Link Developer Preview features
Connectivity Link introduces the API controller 1.0 Developer Preview, which is based on the Apicurio community project and includes 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.
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. Upgrading to Connectivity Link 1.0.2
You can upgrade from Connectivity Link 1.0.x to Connectivity Link 1.0.2 by using the OperatorHub in the OpenShift web console.
1.4.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, if it does not already exist:
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-password- Repeat this step in each Gateway namespace in which a RateLimitPolicy or AuthPolicy is deployed.
1.4.2. Upgrading to Connectivity Link 1.0.2 in the web console
Prerequisites
- You already have Connectivity Link 1.0.x installed on OpenShift 4.16 or later.
- For RateLimitPolicy or AuthPolicy only, you have performed the steps in Section 1.4.1, “Authenticating to registry.redhat.io for Wasm plug-in access”.
Procedure
- Click Operators > Installed Operators > Red Hat Connectivity Link.
-
Ensure that 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.0.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}}}'
Additional resources
- For more information, see Updating installed Operators.
1.5. Connectivity Link resolved issues
| Issue | Description |
|---|---|
| Connectivity Link 1.0.1 cannot be installed on a newly created OpenShift cluster. Previously, Authorino 1.2.1 made one of the Connectivity Link 1.0.1 dependencies unavailable, and the Connectivity Link 1.0.1 constraints were not met. This issue did not affect existing Connectivity Link 1.0.1 installations. Now, the Connectivity Link 1.0.2 dependencies are available and the constraints are met. | |
| Connectivity Link is not available for Microsoft Azure Red Hat OpenShift. Previously, Connectivity Link was not available for Azure Red Hat OpenShift due to the lack of support for OpenShift Container Platform 4.16 or 4.17 in Azure. Now, OpenShift 4.16 support is available in Azure and Connectivity Link support for Azure Red Hat OpenShift has been added. For more information, see What’s new with Azure Red Hat OpenShift? |
| Issue | Description |
|---|---|
| Support protected container registry when loading wasm-shim image.
Previously, for AuthPolicy and RateLimitPolicy, Connectivity Link did not support a protected container registry when the loading wasm-shim image. Now, Connectivity Link supports protected registries, and the steps to authenticate to | |
| Certificates not managed by Connectivity Link are deleted. Previously, certificates not managed by Connectivity Link were deleted, even when a TLSPolicy was not configured. Now, these certificates are no longer deleted. | |
| Fix example commands for configuring DNS provider credentials. Previously, Installing Connectivity Link on OpenShift included incorrect example commands for configuring DNS provider credentials. Now, these examples have been fixed. | |
| Duplication of configuring DNS provider secret. Previously, Installing Connectivity Link on OpenShift and Configuring and deploying Gateway policies with Connectivity Link both described how to configure the DNS provider secret. Now, the documentation has been updated to avoid duplication. | |
| Topology: ConfigMap location lookup using wrong URI. Previously, in the OpenShift web console plug-in, the topology location lookup used the wrong URI. Now, the OpenShift console plug-in uses the correct URI. |
1.6. Connectivity Link known issues
The following known issues apply in Connectivity Link 1.0:
Connectivity Link Operator
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.
OpenShift web console plug-in
CONNLINK-289 - Namespace selector in Policies view switches from subnavigation item back to top-level view
In the Policies view, in a specific policy list, for example, DNS policies, when you switch namespace, you return to the All Policies view. Instead, you should switch namespace and stay in the original specific policy list.
'%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}