Change max pods per node on cli
See original GitHub issueChange max pods per node on cli
Problem
i’m facing problem in my AKS, as i found max pods number is 30 per node, when i checked the deployed pods I found ±10 pods are related to AKS system itself, i think max pods number should not include AKS system pods as this reduced my limit to 20 not 30 as mentioned in MS doc.
Expectative:
run az aks nodepool update --cluster-name <you aks cluster name> --name <pool name> --max-pods=$maxpodsize
(currently it doesn’t work)
Workaround:
-
I created an new node pool
az aks nodepool add --cluster-name <you aks cluster name> -g <your-aks-resource-group> --max-pods $maxpodsize --name newpool --enable-cluster-autoscaler --min-count 1 --max-count 1 -c 1 -s <machine size>
-
Scale down the node of agentpool one per one and scale up newpool as necessary
Workaround problem:
I tried to remove the default pool, but the cli show an error
The message is: Operation failed with status: ‘Bad Request’. Details: There has to be at least one system agent pool.
Workaround Expectative:
Cleaning the default pool if other pool was work
Issue Analytics
- State:
- Created 3 years ago
- Comments:9 (4 by maintainers)
Top GitHub Comments
But why can’t you update the maximum number of pods for an existing nodepool? Could this be added to the cli, please?
The max pod setting per node is user defined and done so at create time only for each agent pool. There is no update functionality for it as seen from the possible commands on update:
Clusters require at least 1 system pool, as returned in err msg. This is detailed here: https://docs.microsoft.com/en-us/azure/aks/use-system-pools