Cloudera Data Engineering Azure node pool migration product advisory

Cloudera Data Engineering product advisory details node pool migration pathways, infrastructure adjustments, and instance replacement mappings for Microsoft Azure previous-generation virtual machine instance types (v1-v4). Cloudera Data Engineering hotfix 1.26.1-H1 is released to ensure continued service stability and performance after Microsoft Azure announced capacity constraints impacting previous-generation virtual machine (VM) instance types (v1-v4) effective July 31, 2026. This update covers the necessary infrastructure adjustments and migration guidelines.

For more information on the Microsoft Azure announcement, see the official details on D8s_v4 limitations in the Azure Previous-generation VM size series capacity limitations and migration guidance page.

Changes for new clusters

Cloudera Data Engineering clusters newly provisioned on Azure will use the v5 instance series (Standard_D8s_v5) for infrastructure node pools. This proactive architectural shift ensures that new deployments remain unaffected by upcoming capacity constraints, while leveraging enhanced performance metrics.

Regarding compute node pools, the selection remains available during service creation.

Table 1. Instance type changes
Scenario Before After
Infrastructure Standard_D8s_v4 Standard_D8s_v5
DB dev/light Standard_D2ds_v4 Standard_D2ads_v5
DB heavy Standard_D8ds_v4 Standard_D8ads_v5
Compute choose v1-v5 choose v5-v7

Pricing

For information on pricing, see the Azure VM pricing page.

In-place upgrade for existing clusters

Cloudera Data Engineering provides the in-place upgrade option for existing clusters, which automatically migrates the affected node pools to unrestricted v5+ instance series.

The infrastructure node pools are migrated to use the Standard_D8s_v5 instance type. With respect to compute node pools, instances are transitioned to a similar, but newer type within the same series. Refer to the Instance type replacement mapping tables for the comprehensive mapping details.

Migration is accomplished during upgrade by deleting the node pool with affected instance type and creating a new node pool with v5+ series instance type. All the IG configurations are preserved in the new node pool.

For more information, see Upgrading Cloudera Data Engineering for guidance on the upgrade process.

Backup and restore for existing clusters

If you cannot perform an in-place upgrade, backup and restore serves as a fallback option.

Similar to in-place upgrade, the restored cluster uses Standard_D8s_v5 for the infrastructure node pools. For compute node pools, instances are mapped based on the type chosen in the original cluster, as described in the Instance type replacement mapping tables.

If Airflow connections and variables are not used in the cluster, see Handling upgrade failures for Cloudera Data Engineering for guidance on the backup and restore process. Otherwise, see Using the backup-restore-based upgrade script to perform the script-based backup and restore.

Instance type replacement mapping

Table 2. Instance type replacement mapping
Category Legacy Series Target Series

Memory optimized

Standard_E8s_v3 Standard_E8s_v5
Standard_E8s_v4 Standard_E8s_v5
Standard_E8as_v4 Standard_E8as_v5
Standard_E16s_v3 Standard_E16s_v5
Standard_E16s_v4 Standard_E16s_v5
Standard_E16as_v4 Standard_E16as_v5
Standard_E20as_v4 Standard_E20as_v5
Standard_E32s_v3 Standard_E32s_v5
Standard_E32s_v4 Standard_E32s_v5
Standard_E32as_v4 Standard_E32as_v5
Standard_E48as_v4 Standard_E48as_v5
Standard_E64s_v3 Standard_E64s_v5
Standard_E64s_v4 Standard_E64s_v5
Standard_E64as_v4 Standard_E64as_v5
Standard_E96as_v4 Standard_E96as_v5
General purpose Standard_D8s_v4 Standard_D8s_v5
Standard_D8as_v4 Standard_D8as_v5
Standard_D16s_v4 Standard_D16s_v5
Standard_D16as_v4 Standard_D16as_v5
Standard_D32s_v4 Standard_D32s_v5
Standard_D32as_v4 Standard_D32as_v5
Standard_D48as_v4 Standard_D48as_v5
Standard_D64s_v4 Standard_D64s_v5
Standard_D64as_v4 Standard_D64as_v5
Compute optimized Standard_F8s_v2 Standard_D8ls_v5
Standard_F16s_v2 Standard_D16ls_v5
Standard_F32s_v2 Standard_D32ls_v5
Standard_F48s_v2 Standard_D48ls_v5
Standard_F72s_v2 Standard_D96ls_v5
Table 3. Database instance type replacement mapping
Category Legacy series Target series
DevDuty Standard_D2ds_v4 Standard_D2ads_v5
LightDuty Standard_D2ds_v4 Standard_D2ads_v5
HeavyDuty Standard_D8ds_v4 Standard_D8ads_v5