pjlewisuk
commented
1 year ago After some further investigation, the issue seems to be related to the network configuration. By default, ASK Construction helper selects "Custom networking" on the "Networking Details" tab, and it seems the default CIDR / subnet configuration doesn't align with the default AKS CIDR / subnet configuration, which means the nodes can't communicate with the control plane?
Verified by changing the VNET option to "Default Networking" and running a similar (but slightly different) command:
az group create -l EastUS -n az-k8s-l4w8-rg
az deployment group create -g az-k8s-l4w8-rg --template-uri https://github.com/Azure/AKS-Construction/releases/download/0.10.0/main.json --parameters \
resourceName=az-k8s-l4w8 \
upgradeChannel=stable \
AksPaidSkuForSLA=true \
SystemPoolType=Standard \
agentCountMax=20 \
enable_aad=true \
AksDisableLocalAccounts=true \
enableAzureRBAC=true \
adminPrincipalId=$(az ad signed-in-user show --query id --out tsv) \
registries_sku=Premium \
acrPushRolePrincipalId=$(az ad signed-in-user show --query id --out tsv) \
omsagent=true \
retentionInDays=30 \
networkPolicy=azure \
azurepolicy=audit \
authorizedIPRanges="[\"1.2.3.4/32\"]" \
ingressApplicationGateway=true \
aksOutboundTrafficType=natGateway \
keyVaultAksCSI=true \
keyVaultCreate=true \
keyVaultOfficerRolePrincipalId=$(az ad signed-in-user show --query id --out tsv)Note lack of the following parameters:
custom_vnet=true
availabilityZones="[\"1\",\"2\",\"3\"]"
appGWcount=0
appGWsku=WAF_v2
appGWmaxCount=10
appgwKVIntegration=true
createNatGateway=trueThis command deployed a cluster successfully.
Describe the bug When deploying and AKS cluster using the latest 0.10.0 version of AKS-C, I receive an error like
"InvalidTemplate","message":"Deployment template parse failed: 'Error converting value \"1\" to type 'System.String[]'. Path '[0]'.'.To Reproduce Go to https://azure.github.io/AKS-Construction and run the commands provided as part of the default configuration for "I want a managed environment" and "Cluster with additional security controls".
The only setting I changed was the region I'm deploying into: US East instead of West Europe.
I'm running the commands on zsh on WSL, but running the PowerShell commands in PowerShell returns the same error
(I've redacted my IP address below, but I'm passing in a valid IP there).
Full error received:
By comparison, a "barebones" command like the one below succeeds:
Expected behavior The cluster should get created without the errors :)
Screenshots If applicable, add screenshots to help explain your problem.
Additional context Add any other context about the problem here.