Pre-flight SKU availability check
Learn about the pre-flight SKU availability check, the possible outcomes, the behaviour, and the actions you need to take.
Before upgrading node pools to a new instance type, Cloudera Data Engineering runs a pre-flight check to confirm that the target SKU is available in your Azure subscription and region. This prevents a scenario where an existing node pool is deleted but the replacement cannot be created due to an unavailable SKU.
If the check fails, for any planned migration, the upgrade stops immediately. No node pools are deleted, the cluster remains operational, and the error message identifies the unavailable SKU and the entitlement you can enable to skip the migration.
| Outcome | Meaning | Action |
|---|---|---|
| Success | The target SKU is available and unrestricted | Upgrade proceeds normally |
| Subscription restriction | The SKU exists in the region but it is blocked by a quota limit or Azure Policy | Request a quota increase, or enable
DE_AZURE_LEGACY_WORKLOAD_INSTANCE_TYPE |
| Not available in region | The SKU is not offered in your Azure region | Enable DE_AZURE_LEGACY_WORKLOAD_INSTANCE_TYPE |
In both failure cases, the error message includes guidance to enable
DE_AZURE_LEGACY_WORKLOAD_INSTANCE_TYPE to skip the instance type migration.
Operations not covered by this check:
- Database upgrade: The database is updated in-place without deleting the existing instance. If the SKU update fails, the database stays on its current SKU safely, so no pre-flight check is needed.
- Cluster restore: During a restore, instance types are remapped in memory, and no node pools are deleted. The destructive replacement scenario cannot occur, so the check does not apply.
