1.8. Upgrading by using the operator
You control your Red Hat Advanced Cluster Management for Kubernetes upgrades by using the operator subscription settings in the Red Hat OpenShift Container Platform console. When you initially deploy Red Hat Advanced Cluster Management by using the operator, you make the following selections:
- Channel - Corresponds to the version of the product that you are installing. The initial channel setting is often the most current channel that was available at the time of installation.
-
Approval - Specifies whether approval is required for updates within the channel, or if they are done automatically. If set to
Automatic
, then minor release updates in the selected channel are deployed without administrator intervention. If theManual
setting is selected, then each update to the minor release within the channel requires an administrator to approve the update.
You also use those settings when you upgrade Red Hat Advanced Cluster Management by using the operator.
Required access: OpenShift Container Platform administrator
Complete the following steps to upgrade your operator:
- Log in to your OpenShift Container Platform operator hub.
- In the OpenShift Container Platform navigation, select Operators > Installed operators.
- Select the Red Hat Advanced Cluster Management for Kubernetes operator.
- Select the Subscription tab to edit the subscription settings.
Ensure that the Upgrade Status is labeled Up to date. This status indicates that the operator is at the latest level that is available in the selected channel. If the Upgrade Status indicates that there is an upgrade pending, complete the following steps to update it to the latest minor release that is available in the channel:
- Click the Manual setting in the Approval field to edit the value.
- Select Automatic to enable automatic updates.
- Select Save to commit your change.
- Wait for the automatic updates to be applied to the operator. The updates automatically add the required updates to the latest version in the selected channel. When all of the updates are complete, the Upgrade Status field indicates Up to date.
- Now that the Upgrade Status is Up to date, click the value in the Channel field to edit it.
Select the channel for the next available feature release. You cannot skip channels when upgrading.
Important: You cannot revert back to an earlier version after upgrading to a later version in the channel selection. You must uninstall the operator and reinstall an earlier version to use it.
- Select Save to save your changes.
- Wait for the automatic upgrade to complete. After the upgrade to the next feature release completes, the updates to the latest patch releases within the channel are deployed.
- If you have to upgrade to a later feature release, repeat steps 7-9 until your operator is at the latest level of the desired channel. Make sure that all of the patch releases are deployed for your final channel.
- Optional: You can set your Approval setting to Manual, if you want your future updates within the channel to require manual approvals.
Red Hat Advanced Cluster Management is running at the latest version of the selected channel.
1.8.1. Upgrading OpenShift Container Platform 复制链接链接已复制到粘贴板!
You can upgrade the version of Red Hat OpenShift Container Platform that hosts your Red Hat Advanced Cluster Management for Kubernetes hub cluster. Back up your data before initiating any cluster-wide upgrade.
During the upgrade of the OpenShift Container Platform version, the Red Hat Advanced Cluster Management web console might show brief periods when pages or data are unavailable. Indicators can include HTTP 500 (Internal Server Error), HTTP 504 (Gateway Timeout Error), or errors that data that was previously available is not available. This is a normal part of the upgrade, and no data is lost when this occurs. The availability is eventually restored.
The search index is also rebuilt during this upgrade, so any queries that are submitted during the upgrade might be incomplete.
The following table contains some noted observations from an upgrade from OpenShift Container Platform version 4.4.3 to 4.4.10:
Elapsed time of upgrade process (minutes:seconds) | Observed change | Duration |
---|---|---|
03:40 | Governance and risk console experiences HTTP 500 | Service restored within 20 seconds |
05:30 | AppUI experiences HTTP 504 Gateway Timeout | Service restored within 60 seconds |
06:05 | Cluster+Search UI experience HTTP 504 Gateway Timeout | Service restored within 20 seconds |
07:00 | Cluster+Search UI experience HTTP 504 Gateway Timeout | Service restored within 20 seconds |
07:10 | Topology+Cluster UI Display error messages within the page | Service restored within 20 seconds |
07:35 | HTTP 500 for most UI pages | Service restored within 60 seconds |
08:30 | Service restored for all pages |