High-level upgrade steps

Refer to this section for high-level upgrade steps and links to more detailed upgrade documentation. This document is not meant to provide you with complete upgrade steps, but rather it outlines the general upgrade path and provides you with the links to existing upgrade documentation.

important

Each of these operation has its own prerequisites and postrequisites so in addition to the actual upgrade steps, the prerequisites and postrequisites need to be performed as well.
You will need to upgrade all Data Lakes and Cloudera Data Hub clusters separately, first the Data Lakes and then each Cloudera Data Hub cluster.
For Data Lakes, the Runtime and OS upgrade is performed in one step. For Cloudera Data Hub clusters, the Cloudera Runtime needs to be updated first, and then the OS in a separate step.
You can perform each upgrade operation either from the Upgrade UI of the respective cluster or using the Cloudera CLI.
The upgrade user interface in the Cloudera Management Console shows you the next Data Lake and Cloudera Data Hub upgrade step available, so you can refer to it as a guideline.

Depending on the upgrade paths you have identified in Resizing to Enterprise Data Lake if using Medium Duty Data Lake, you need to start the upgrade procedure at different points as follows:

If the Cloudera Runtime version of your Data Lake and Cloudera Data Hub clusters is 7.2.17.100 or earlier, you need to start at Upgrading to a supported version.
If the Cloudera Runtime version of your Data Lake and Cloudera Data Hub clusters is 7.2.17.200-7.2.17.500, you can proceed to Resizing to Enterprise Data Lake if using Medium Duty Data Lake.
If the Cloudera Runtime version of your Data Lake and Cloudera Data Hub clusters is 7.2.18.100-7.2.18.200, you can proceed to Upgrading Data Lake Cloudera Runtime to 7.3.1. and OS to RHEL 8.10.