3.3. Performing a Control Plane Only update

Procedure

1. Using the web console, update any Operator Lifecycle Manager (OLM) Operators to the versions that are compatible with your intended updated version. For more information, see "Updating installed Operators".

2. Verify that all machine config pools display a status of Up to date and that no machine config pool displays a status of UPDATING.

   To view the status of all machine config pools, click Compute MachineConfigPools and review the contents of the Update status column.

   注意

   If your machine config pools have an Updating status, wait for this status to change to Up to date. This process could take several minutes.

3. Set your channel to eus-<4.y+2>.

   To set your channel, click Administration Cluster Settings Channel. You can edit your channel by clicking on the current hyperlinked channel.

4. Pause all worker machine pools except for the master pool. You can perform this action on the MachineConfigPools tab under the Compute page. Select the vertical ellipses next to the machine config pool you’d like to pause and click Pause updates.
5. Update to version <4.y+1> and complete up to the Save step. For more information, see "Updating a cluster by using the web console".
6. Ensure that the <4.y+1> updates are complete by viewing the Last completed version of your cluster. You can find this information on the Cluster Settings page under the Details tab.
7. If necessary, update your OLM Operators by using the Administrator perspective on the web console. For more information, see "Updating installed Operators".
8. Update to version <4.y+2> and complete up to the Save step. For more information, see "Updating a cluster by using the web console".
9. Ensure that the <4.y+2> update is complete by viewing the Last completed version of your cluster. You can find this information on the Cluster Settings page under the Details tab.

10. Unpause all previously paused machine config pools. You can perform this action on the MachineConfigPools tab under the Compute page. Select the vertical ellipses next to the machine config pool you’d like to unpause and click Unpause updates.

    重要

    If pools are paused, the cluster is not permitted to upgrade to any future minor versions, and some maintenance tasks are inhibited. This puts the cluster at risk for future degradation.

11. Verify that your previously paused pools are updated and that your cluster has completed the update to version <4.y+2>.

    You can verify that your pools have updated on the MachineConfigPools tab under the Compute page by confirming that the Update status has a value of Up to date.

    重要

    When you update a cluster that contains Red Hat Enterprise Linux (RHEL) compute machines, those machines temporarily become unavailable during the update process. You must run the upgrade playbook against each RHEL machine as it enters the NotReady state for the cluster to finish updating. For more information, see "Updating a cluster that includes RHEL compute machines".

    You can verify that your cluster has completed the update by viewing the Last completed version of your cluster. You can find this information on the Cluster Settings page under the Details tab.

Procedure

1. Using the web console, update any Operator Lifecycle Manager (OLM) Operators to the versions that are compatible with your intended updated version. You can find more information on how to perform this action in "Updating installed Operators"; see "Additional resources".

2. Verify that all machine config pools display a status of UPDATED and that no machine config pool displays a status of UPDATING. To view the status of all machine config pools, run the following command:

   $ oc get mcp

   Example output

   NAME     CONFIG                                         	UPDATED   UPDATING
   master   rendered-master-ecbb9582781c1091e1c9f19d50cf836c       True  	  False
   worker   rendered-worker-00a3f0c68ae94e747193156b491553d5       True  	  False

3. Your current version is <4.y>, and your intended version to update is <4.y+2>. Change to the eus-<4.y+2> channel by running the following command:

   $ oc adm upgrade channel eus-<4.y+2>

   注意

   If you receive an error message indicating that eus-<4.y+2> is not one of the available channels, this indicates that Red Hat is still rolling out EUS version updates. This rollout process generally takes 45-90 days starting at the GA date.

4. Pause all worker machine pools except for the master pool by running the following command:

   $ oc patch mcp/worker --type merge --patch '{"spec":{"paused":true}}'

   注意

   You cannot pause the master pool.

5. Update to the latest version by running the following command:

   $ oc adm upgrade --to-latest

   Example output

   Updating to latest version <4.y+1.z>

6. Review the cluster version to ensure that the updates are complete by running the following command:

   $ oc adm upgrade

   Example output

   Cluster version is <4.y+1.z>
   ...

7. Update to version <4.y+2> by running the following command:

   $ oc adm upgrade --to-latest

8. Retrieve the cluster version to ensure that the <4.y+2> updates are complete by running the following command:

   $ oc adm upgrade

   Example output

   Cluster version is <4.y+2.z>
   ...

9. To update your worker nodes to <4.y+2>, unpause all previously paused machine config pools by running the following command:

   $ oc patch mcp/worker --type merge --patch '{"spec":{"paused":false}}'

   重要

   If pools are not unpaused, the cluster is not permitted to update to any future minor versions, and some maintenance tasks are inhibited. This puts the cluster at risk for future degradation.

10. Verify that your previously paused pools are updated and that the update to version <4.y+2> is complete by running the following command:

    $ oc get mcp

    重要

    When you update a cluster that contains Red Hat Enterprise Linux (RHEL) compute machines, those machines temporarily become unavailable during the update process. You must run the upgrade playbook against each RHEL machine as it enters the NotReady state for the cluster to finish updating. For more information, see "Updating a cluster that includes RHEL compute machines" in the additional resources section.

    Example output

    NAME 	   CONFIG                                            UPDATED     UPDATING
    master   rendered-master-52da4d2760807cb2b96a3402179a9a4c    True  	 False
    worker   rendered-worker-4756f60eccae96fb9dcb4c392c69d497    True 	 False

1. You have updated all Operators previously installed through Operator Lifecycle Manager (OLM) to a version that is compatible with your target release. Updating the Operators ensures they have a valid update path when the default software catalogs switch from the current minor version to the next during a cluster update. See "Updating installed Operators" for more information on how to check compatibility and, if necessary, update the installed Operators.
2. Confirm the cluster version compatibility between the current and intended Operator versions. You can verify which versions your OLM Operators are compatible with by using the Red Hat OpenShift Container Platform Operator Update Information Checker.

1. Pause the worker machine pools.
2. Update OpenShift Container Platform from <4.y> to <4.y+1>.
3. Update ODF from <4.y> to <4.y+1>.
4. Update OpenShift Container Platform from <4.y+1> to <4.y+2>.
5. Update ODF to <4.y+2>.
6. Unpause the worker machine pools.