I have a Kubernetes cluster that I'm trying to add a new node pool to.
I want to use Spot Instances, however I have tried about 6 different VM SKU's and validation always fails with;
The resource with id: '/subscriptions/REDACTED/resourceGroups/MC_innerloop_aks-az-k8s-kanp_westeurope/providers/Microsoft.Compute/virtualMachineScaleSets/aks-npuser01-41715184-vmss' failed validation with message: 'The requested size for resource '/subscriptions/REDACTED/resourceGroups/MC_innerloop_aks-az-k8s-kanp_westeurope/providers/Microsoft.Compute/virtualMachineScaleSets/aks-npuser01-41715184-vmss' is currently not available in location 'westeurope' zones '' for subscription 'REDACTED'. Please try another size or deploy to a different location or zones.
I have looked at the az vm list-skus
feature of the Azure CLI - however it doesn't seem to cater for Spot Instances.
I have verified that;
- I have Quota available in WestEurope for the VM SKU's as per the Portal Quota screen
- I have Spot Instance Quota available in the subscription (20 unused).
- I've tried with AZ's and Without.
- I've tried EastUs region as well as WestEurope
- I have tried using the Azure Portal to create the pool, as well as bicep
- Creating a Node Pool of the same SKU + Region + Zone config (but without
Spot
) works fine
Whilst I can write a script to pull all available SKU's in Azure (from az vm list-skus
), and iteratively try creating my Spot Node Pool it feels like there must be a better way.
Can someone advise a better method of finding an available Spot VM?