Skip to content
This repository has been archived by the owner on Nov 30, 2021. It is now read-only.

Not all ACS locations actually available for k8s #761

Closed
mboersma opened this issue Mar 8, 2017 · 2 comments
Closed

Not all ACS locations actually available for k8s #761

mboersma opened this issue Mar 8, 2017 · 2 comments
Labels

Comments

@mboersma
Copy link
Member

mboersma commented Mar 8, 2017

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.

@mboersma mboersma added the bug label Mar 8, 2017
@bacongobbler
Copy link
Member

I actually opened an issue on the azure cli for this as well: Azure/azure-cli#2396

@Cryptophobia
Copy link

This issue was moved to teamhephy/workflow#29

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants