I'm trying to use ARM template to manage the deployment of AKS resources and got following questions thru some experiments by using these attached template:
91541-aks-agentpoolsjson.txt
91542-aks-agentpools-parametersjson.txt
91551-aks-clusterjson.txt
91543-aks-cluster-parametersjson.txt
Changes of node pools in existing cluster template
I used the attached aks_cluster.json and aks_cluster_parameters.json to create AKS cluster (1 node pool with 2 nodes), then I changed the "count" in aks_cluster_parameters.json to 3 and made the deployment again by using these 2 json files, I can see the deployment was successful and there were 3 nodes in that node pool. Does it mean that configurations of node pool, at least some of them, can be updated in the existing template? Though https://docs.microsoft.com/en-gb/azure/aks/use-multiple-node-pools#manage-node-pools-using-a-resource-manager-template says it only can be done thru a separate templateAdding and deleting node pools in template
On the AKS cluser created in 1), I added a new agent pool (agentpool2) by using the attached aks_agentpools.json and aks_agentpools_parameters.json, where the configuration of agentpool2 was added as the 2nd item of array. This adding operation was successful. However, when I tried to delete agentpool2 by removing it from that array then making a deployment by using these 2 json files, I can see agentpool2 is still there. Does it mean that ARM template can support adding node pool only but not deleting node pool?What configuration of node pool can be changed/updated after it is created.
For the configurations of a node pool listed on https://docs.microsoft.com/en-us/azure/templates/microsoft.containerservice/managedclusters/agentpools?tabs=json#ManagedClusterAgentPoolProfileProperties, which of them can be changed and which of them can be changed thru ARM template, after a node pool is created? I tried to change the vmSize and maxPods thru template but failed. Is it documented somewhere? If no, can I request to document it somewhere?About "enableAutoScaling"
I enabled "enableAutoScaling" on an existing node pool with 5 nodes and provided "minCount" as 2 and "maxCount" as 6 accordingly in template. After deployment, 3 nodes were still there which I think is expected.
Then I disabled it and removed "minCount" and "maxCount" in template. After deployment, I can see "enableAutoScaling" was disabled thru running "az aks nodepool show", but the node count was still 3 though the "count" property of agent pool was 5 in template. It seems to me that "count" property was not respected after disabling "enableAutoScaling", may I know why?
