New cluster creation behaviour

Learn about the new cluster creation behaviour when the workload and database entitlements are enabled or disabled.

Workload entitlement disabled (default)

The UI instance-type selector displays current v5 SKUs as selectable options and marks v3/v4 SKUs as hidden ones.
Cloudera Data Engineering selects Standard_D8s_v5 for base/app/app2 node pools (system default General/Small) and uses the user-selected instance type for comp/cmp2 node pools.
The create cluster validation checks the user-selected instance type against the current v5+ instance collection.

The UI instance-type selector displays v3/v4 SKUs as selectable options, and marks v5 SKUs as hidden ones.
Cloudera Data Engineering selects Standard_D8s_v4 for base/app/app2 node pools and uses the user-selected legacy type for comp/cmp2 node pools.
The create cluster validation checks the user-selected instance type against legacy instance collection.

Cloudera Data Engineering selects the default v5 SKU: Standard_D2ads_v5 for DevDuty/LightDuty deployments, and Standard_D8ads_v5 for HeavyDuty deployments.
Cloudera Data Engineering queries the Azure MySQL Flexible Server Location Capabilities API, filters out v1–v4 SKUs, attempts to use the preferred default SKU, and falls back to the first available v5 SKU candidate.
Built-in availability check: the Capabilities API returns only SKUs available in the region and subscription and no separate pre-flight check is needed for database creation.

Cloudera Data Engineering selects the legacy default SKU: Standard_D2ds_v4 for DevDuty/LightDuty deployments, Standard_D8ds_v4 for HeavyDuty deployments from legacy instance types.
Cloudera Data Engineering queries the Capabilities API without filtering out v1–v4 SKUs, allowing legacy SKUs to be included in the candidate set.
The system then selects the legacy default instance. If the legacy default is unavailable in the region, the system falls back to the first available candidate.