| name | kickstart-cluster-status |
| description | Non-blocking cluster status peek — run at the end of Phases 3, 4, 5 to check AKS provisioning progress without hanging. |
| disable-model-invocation | true |
Cluster Status Check
A non-blocking peek at the background cluster provision. Run at the end of Phases 3, 4, and 5. Wrap in timeout to prevent hanging.
timeout 15 az aks show --name <cluster> --resource-group <rg> --subscription <sub> --query "{state:provisioningState, power:powerState.code}" --output json --only-show-errors
If timed out (exit 124), skip and retry next phase.
Succeeded: Attach ACR if not done yet (use the ACR attachment approach from /kickstart-handoff, step 6c). Remember this for Phase 6.Creating: Note it, continue.Failed: Get details from az monitor activity-log list --resource-group <rg> --status Failed --max-events 3. Common failures:
- "could not find a suitable VM size": The region is out of capacity, or the subscription lacks quota for the D-family SKUs AKS Automatic needs. These look the same because AKS Automatic provisions nodes on AKS-owned (HOBO) subscriptions, so the shortage can be on the AKS side even when your own quota is fine. Suggest retrying in a lower-contention region, in priority order:
eastus2, westus3, southcentralus, canadacentral, swedencentral. Avoid eastus, westeurope, and southeastasia — they carry the most capacity pressure. Link to quota page: https://portal.azure.com/#view/Microsoft_Azure_Capacity/QuotaMenuBlade/~/myQuotas
- QuotaExceeded: Suggest different region or quota increase.
- OperationNotAllowed: Provider not registered or policy blocking.
- InvalidParameter: Bad name — re-collect from user.
Offer retry via
vscode_askQuestions.
- 404:
az aks create may have failed silently. Check the RG exists, retry creation.
Also check ACR:
timeout 15 az acr show --name <acr> --resource-group <rg> --subscription <sub> --query provisioningState --output tsv --only-show-errors
