Identify your upgrade path

Refer to the following diagram for a high-level overview of the upgrade steps. Your starting point will vary, depending on the Cloudera Runtime version and image version that your environment, Data Lake, and Cloudera Data Hub clusters are using.

High-level upgrade steps for Cloudera Runtime 7.3.1.200 SP1

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.

The high-level upgrade steps are presented horizontally with the different step-in points identified in medium gray boxes:

If you are using Cloudera Runtime 7.3.1 or 7.3.1.100 CHF1, you can directly upgrade to Cloudera Runtime 7.3.1.200 SP1 using the steps for Performing a Cloudera Data Hub service pack upgrade.

As presented in the diagram, you can directly upgrade to Cloudera Runtime 7.3.1.200 SP1 from the following versions:

7.2.17.200 and higher versions
7.2.18 and its services packs

This means that you need to complete the following steps to upgrade your Data Lake and Cloudera Data Hub to Cloudera Runtime 7.3.1.200 SP1:

Upgrade database to PostgreSQL 14 - if you are currently using a lower version than PostgreSQL 14
Upgrade Data Lake Cloudera Runtime to 7.3.1 and OS to RHEL 8.10
Upgrade Cloudera Runtime version of Cloudera Data Hub clusters to 7.3.1

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 CDP 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.

There is no supported direct upgrade path to Cloudera Runtime 7.3.1.200 SP1 in the following cases:

from Cloudera Runtime 7.2.16 and its service packs
from Cloudera Runtime 7.2.17 and 7.2.17.100

If the Cloudera Runtime version of your Data Lake and Cloudera Data Hub clusters is 7.2.17.100 or lower, refer to the Cloudera Runtime 7.3.1 and 7.3.1.100 CHF1 upgrade path below to upgrade to a supported version from which you can upgrade to Cloudera Runtime 7.3.1.200 SP1.

High-level upgrade steps for Cloudera Runtime 7.3.1 and 7.3.1.100 CHF1

The high-level upgrade steps are presented horizontally with the different step-in points identified in medium gray boxes:

As presented in the diagrams, you may be required to perform the following operations:

Runtime service pack upgrades for your Data Lake and each Cloudera Data Hub cluster
Major/Minor Runtime and OS upgrades for your Data Lake and each Cloudera Data Hub cluster
CentOS to RHEL 8 upgrade for your FreeIPA, Data Lake, and each Cloudera Data Hub cluster
Database PostreSQL version upgrade
Data Lake resize

For example, if you are starting with Cloudera Runtime 7.2.16 and your Data Lake is Medium Duty, you need to have your Data Lake and all Cloudera Data Hub clusters upgraded to the latest service pack of Cloudera Runtime 7.2.16 first, then you need to upgrade FreeIPA to RHEL 8, upgrade Data Lake and Cloudera Data Hub clusters to 7.2.17.500, upgrade the database to PostgreSQL 14, resize your Data Lake to Enterprise Data Lake, then upgrade Data Lake to Cloudera Runtime 7.3.1 and RHEL 8.10, then Upgrade Cloudera Data Hub clusters to Runtime 7.3.1, and finally, upgrade Cloudera Data Hub clusters to RHEL 8.10.

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, 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.