Not all ACS locations actually available for k8s

[Cryptophobia]

From @mboersma on March 8, 2017 15:55

In the Azure Quick Start docs, we suggest running this command to discover what locations exist for container services:

$ az account list-locations --query [].name --output tsv
eastasia
southeastasia
centralus
eastus
eastus2
westus
northcentralus
southcentralus
northeurope
westeurope
westus2
....

However, many of those locations will later fail when trying to actually create the service:

$  az acs create --resource-group="${AZURE_RG_NAME}" --location="${AZURE_DC_LOCATION}" \
>   --orchestrator-type=kubernetes --master-count=1 --agent-count=1 \
>   --agent-vm-size="Standard_D2_v2" \
>   --admin-username="matt" \
>   --name="${AZURE_SERVICE_NAME}" --dns-prefix="mboersma" \
>   --ssh-key-value @/Users/matt/.ssh/id_rsa.pub
creating service principal.........done
waiting for AAD role to propagate.done
The provided location 'westus2' is not available for resource type 'Microsoft.ContainerService/containerServices'. List of available regions for the resource type is 'japaneast,centralus,eastus2,japanwest,eastasia,southcentralus,australiaeast,australiasoutheast,brazilsouth,southeastasia,westus,northcentralus,westeurope,northeurope,eastus'.  

The first command should be replaced with one that lists only the appropriate regions.

Copied from original issue: deis/workflow#761

[Cryptophobia]

From @bacongobbler on March 8, 2017 16:12

I actually opened an issue on the azure cli for this as well: https://github.com/Azure/azure-cli/issues/2396