Cloudera Data Engineering upgrade version compatibility
Cloudera Data Engineering provides the in-place upgrade option from the eligible versions to the latest version. If you are on a version that is ineligible for in-place upgrade, the in-place upgrade option is disabled and you can perform a backup and restore.
Checking your upgrade options
To check if your Cloudera Data Engineering version is eligible for the in-place upgrade option, see Support lifecycle policy.
In-place upgrades
To perform an in-place upgrade, you must be on a version eligible for the in-place upgrade option. The Cloudera Data Engineering versions eligible for in-place upgrade table includes the specific AWS and Azure versions from which you can perform an in-place upgrade to the latest Cloudera Data Engineering version.
| Supported upgrade versions | Target version |
|---|---|
|
Azure: 1.23.0 and higher AWS: 1.23.0 and higher |
1.24.1 |
Backup and restore
If you are on a version that is not eligible for the in-place upgrade option, to upgrade to the latest version, create a new Cloudera Data Engineering service and transfer your jobs to the new service by following the instructions in Backing up and restoring Cloudera Data Engineering jobs.
Runtime component version behavior after upgrading
To maintain backwards compatibility, the in-place upgrade does not modify the image type, and after the upgrade to Cloudera Data Engineering version 1.24.1, the old RedHat (deprecated) images continue to be used. To use the new, security hardened image, after the upgrade, you must create new Virtual Clusters and select the new image. For more information on the supported runtime components, see Compatibility for Cloudera Data Engineering and Runtime components.
