question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Change max pods per node on cli

See original GitHub issue

Change 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:

  1. 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>

  2. 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:closed
  • Created 3 years ago
  • Comments:9 (4 by maintainers)

github_iconTop GitHub Comments

6reactions
pvorbcommented, Nov 12, 2020

But why can’t you update the maximum number of pods for an existing nodepool? Could this be added to the cli, please?

5reactions
jlukcommented, May 11, 2020

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:

Command
    az aks nodepool update : Update a node pool to enable/disable cluster-autoscaler or change min-
    count or max-count.

Arguments
    --cluster-name       [Required] : The cluster name.
    --name -n            [Required] : The node pool name.
    --resource-group -g  [Required] : Name of resource group. You can configure the default group
                                      using `az configure --defaults group=<name>`.
    --disable-cluster-autoscaler -d : Disable cluster autoscaler.
    --enable-cluster-autoscaler -e  : Enable cluster autoscaler.
    --max-count                     : Maximum nodes count used for autoscaler, when "--enable-
                                      cluster-autoscaler" specified. Please specify the value in the
                                      range of [1, 100].
    --min-count                     : Minimum nodes count used for autoscaler, when "--enable-
                                      cluster-autoscaler" specified. Please specify the value in the
                                      range of [1, 100].
    --mode                          : The mode for a node pool which defines a node pool's primary
                                      function. If set as "System", AKS prefers system pods
                                      scheduling to node pools with mode `System`. Learn more at
                                      https://aka.ms/aks/nodepool/mode.  Allowed values: System,
                                      User.
    --no-wait                       : Do not wait for the long-running operation to finish.
    --tags                          : Space-separated tags: key[=value] [key[=value] ...]. Use '' to
                                      clear existing tags.
    --update-cluster-autoscaler -u  : Update min-count or max-count for cluster autoscaler.

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

Read more comments on GitHub >

github_iconTop Results From Across the Web

Increase Max pods per node with advanced networking on ...
We need to change the limitation of 30 pods per node as it is very incomprehensible one for us. Before the advanced networking...
Read more >
Managing the maximum number of pods per node
Configuring the maximum number of pods per node. In OpenShift Container Platform, ... List the MachineConfigPool CRDs to see if the change is...
Read more >
How to increase the number of pods limit per Kubernetes ...
How to increase kubernetes 110 pod limit per node or kubernetes max pods limit set by default with kubelet configurations update.
Read more >
Configure maximum Pods per node
This page explains how you can configure the maximum number of Pods that can run on a node for Standard clusters. This value...
Read more >
Managing the maximum number of pods per node
Create a custom resource (CR) for your configuration change. Sample configuration for a max-pods CR · List the MachineConfigPool CRDs to see if ......
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found