After following the instructions to register the Windows AKS feature I see the following error when running "az aks create --resource-group staging-r1-aks --name stagingaks --node-count 2 --enable-addons monitoring --kubernetes-version 1.15.7 --generate-ssh-keys --windows-admin-password password-removed --windows-admin-username azureuser --vm-set-type VirtualMachineScaleSets --load-balancer-sku standard --network-plugin azure"
The behavior of this command has been altered by the following extension: aks-preview
The request content was invalid and could not be deserialized: 'Could not find member 'template' on object of type 'DeploymentDefinition'. Path 'template', line 1, position 12.'.
I am using azure-cli version 2.4.0 * and aks-preview version 0.4.43
⚠Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
Thanks for the question. We are currently investigating and will update you shortly.
same issue here
same issue here
Temporarily, you may bypass this problem by removing the AKS extension preview when you are creating a new AKS cluster.
az extension remove --name aks-preview
first.az aks create --resource-group $RESGROUP --name $CLUSTER --node-count 2 --enable-addons monitoring --kubernetes-version $K8SVER --vm-set-type VirtualMachineScaleSets --load-balancer-sku standard --network-plugin azure --attach-acr $ACR
.az extension add --name aks-preview
)It seems the AKS extension preview generates an outdated ARM template. I hope the problem resolved soon.
same issue here.
@jluk Multiple customers are seeing this issue, discussed here as well: https://github.com/Azure/azure-cli/issues/13121
Can you please share your insights on this issue? Thanks :)
@nboeckmann @msfreaks @john-adkins I am reaching out to the product team.
Meanwhile, please follow the workaround shared in the comment above: https://github.com/MicrosoftDocs/azure-docs/issues/53469#issuecomment-621248236
or Deploy AKS Cluster with Windows node-pool via Azure Portal.
@MikkelHegn for awareness on windows impact from the preview version. The engineering team is investigating the impacted of the preview-extension, but the work around above are valid. The is to remove the preview-extension.
although the workaround in https://github.com/MicrosoftDocs/azure-docs/issues/53469#issuecomment-621248236 is valid, it prevents you from assigning a custom resource group name for the nodes.
The issue only impacts enabling the monitoring addon. You can still run all the commands normally with extensions enabled apart from:
az aks --enable-addons monitoring
az aks enable-addons -a monitoring
There's a fix out for the extension pending merge.
I will close this issue as the issue is being tracked here: https://github.com/Azure/azure-cli/issues/13121
Please follow that thread to track this issue.
Most helpful comment
Temporarily, you may bypass this problem by removing the AKS extension preview when you are creating a new AKS cluster.
az extension remove --name aks-preview
first.az aks create --resource-group $RESGROUP --name $CLUSTER --node-count 2 --enable-addons monitoring --kubernetes-version $K8SVER --vm-set-type VirtualMachineScaleSets --load-balancer-sku standard --network-plugin azure --attach-acr $ACR
.az extension add --name aks-preview
)It seems the AKS extension preview generates an outdated ARM template. I hope the problem resolved soon.