Red Hat SummitChapter 1. Updating Connectivity Link 1.3
You can update your Red Hat Connectivity Link from one version to the next if your supported configuration meets the requirements of the version you want to update to.
1.1. Supported configurations with Red Hat Connectivity Link
Connectivity Link must run on a supported combination of OpenShift Container Platform with Red Hat OpenShift Service Mesh as the Gateway API provider, and use the cert-manager Operator for Red Hat OpenShift. Red Hat provides both production and development support for supported configurations and tested integrations according to your subscription agreement.
1.1.1. Supported OpenShift Container Platform version configurations
| Red Hat Connectivity Link | Red Hat OpenShift Container Platform | Red Hat OpenShift Dedicated | Red Hat OpenShift Service on AWS | Microsoft Azure Red Hat OpenShift |
|---|---|---|---|---|
| Version 1.3 | 4.21, 4.20, 4.19 | 4.21, 4.20, 4.19 | 4.21, 4.20, 4.19 | 4.19 |
| Version 1.2 | 4.20, 4.19, 4.18 | 4.20, 4.19, 4.18 | 4.20, 4.19, 4.18 | 4.17 |
For Microsoft Azure, see the Support lifecycle for Azure Red Hat OpenShift 4.
1.1.2. Supported Operators
| Red Hat Connectivity Link | Red Hat OpenShift Service Mesh | cert-manager Operator for Red Hat OpenShift |
|---|---|---|
| Version 1.3 | 3.2 | 1.18 |
| Version 1.2 | 3.1 | 1.17 |
1.1.3. Supported cloud providers
All versions of Connectivity Link support the following platforms as backing cloud providers for OpenShift Container Platform:
- Amazon Web Services
- Google Cloud Platform
- Microsoft Azure
For more information, see the documentation for your chosen cloud provider.
1.1.4. Supported cloud DNS providers
For DNS policies, all versions of Connectivity Link support the following cloud DNS providers:
- Amazon Route 53
- Google Cloud Platform DNS
- Microsoft Azure DNS
For more information, see the documentation for your chosen cloud DNS provider.
1.1.5. Supported on-premise DNS providers
You can use CoreDNS can to configure an on-cluster DNS zone. For more information, see About using on-premise DNS with CoreDNS.
1.1.6. Supported data stores for rate limiting
For rate limiting policies, Connectivity Link supports the following Redis-based data stores for rate limit counters in multicluster environments:
| Red Hat Connectivity Link | Redis Enterprise or Cloud | Amazon Elasticache | Dragonfly Community or Cloud |
|---|---|---|---|
| Version 1.3 | latest | latest | latest |
| Version 1.2 | latest | latest | latest |
For more information, see the documentation for your chosen Redis-based datastore.
1.1.7. Supported identity access management
For authentication policies, Connectivity Link supports API keys and the following products:
| Red Hat Connectivity Link Version | Red Hat build of Keycloak |
|---|---|
| Version 1.3 | Version 26.4 |
| Version 1.2 | Version 26.4 |
For more information, see Supported Configurations for Red Hat build of Keycloak.
1.2. Updating Connectivity Link with the OpenShift Container Platform web console
You can update from Connectivity Link 1.2.x to Connectivity Link 1.3 by using the OpenShift Container Platform web console. Make sure that the OpenShift Container Platform version you have is compatible with the Connectivity Link version you want to update to. See the Red Hat Connectivity LInk Life Cycle Policy for details about version support and OpenShift Container Platform compatibility.
On OpenShift Container Platform 4.19 or later, if you are updating your cluster from a previous OpenShift Container Platform version that contains Gateway API Custom Resource Definitions (CRDs), you must ensure that these resources exactly match the Gateway API version supported by OpenShift Container Platform 4.19. For more information, see the OpenShift documentation on managing Gateway API resources.
1.3. Updating to Connectivity Link 1.3 in the web console
Update your Red Hat Connectivity Link with the OpenShift Container Platform web console.
Prerequisites
- You already have Connectivity Link 1.2.x installed on OpenShift Container Platform 4.19 or later.
Procedure
- Click Ecosystem > Installed Operators > Red Hat Connectivity Link.
-
Ensure that the Update channel is set to
stable. -
If Update approval is set to Automatic, the update is 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.3 is installed and that your deployment is up and running.
1.4. Using your Red Hat subscription
Red Hat Connectivity Link is provided through a software subscription. To manage your subscriptions, access your account at the Red Hat Customer Portal.
- Go to access.redhat.com.
- If you do not already have an account, create one.
- Log in to your account.
- In the menu bar, click Subscriptions to view and manage your subscriptions.
'%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}