Node pools and scaling in Azure - Commands & Configuration

Introduction

When you run applications in the cloud, you need computers to run them. Node pools let you group these computers with similar settings. Scaling means adding or removing these computers automatically to handle more or less work.

When your app needs more computers during busy times and fewer when quiet to save money

When you want to separate computers by type, like some with more memory and some with more CPU

When you want to update or fix some computers without stopping the whole app

When you want to run different versions of your app on different groups of computers

When you want to control costs by only running the number of computers you need

Config File - nodepool-scale.yaml

nodepool-scale.yaml

apiVersion: azure.microsoft.com/v1
kind: NodePool
metadata:
  name: example-nodepool
  resourceGroup: example-resource-group
spec:
  clusterName: example-aks-cluster
  vmSize: Standard_DS2_v2
  nodeCount: 3
  enableAutoScaling: true
  minCount: 2
  maxCount: 5

This file defines a node pool for an Azure Kubernetes Service (AKS) cluster.

vmSize sets the computer size.

nodeCount is the starting number of computers.

enableAutoScaling turns on automatic scaling.

minCount and maxCount set the limits for scaling.

Commands

This command creates a new node pool named example-nodepool in the AKS cluster example-aks-cluster with 3 nodes. It enables automatic scaling between 2 and 5 nodes with a specific VM size.

Terminal

az aks nodepool add --resource-group example-resource-group --cluster-name example-aks-cluster --name example-nodepool --node-count 3 --enable-cluster-autoscaler --min-count 2 --max-count 5 --node-vm-size Standard_DS2_v2

Expected Output

Operation "Create" started for node pool example-nodepool

Succeeded

→

--node-count - Sets the initial number of nodes

→

--enable-cluster-autoscaler - Turns on automatic scaling

→

--min-count - Minimum number of nodes when scaling

This command lists all node pools in the AKS cluster to verify the new node pool was created and check its status.

Terminal

az aks nodepool list --resource-group example-resource-group --cluster-name example-aks-cluster

Expected Output

[

  {

    "name": "example-nodepool",

    "count": 3,

    "vmSize": "Standard_DS2_v2",

    "enableAutoScaling": true,

    "minCount": 2,

    "maxCount": 5

  }

]

This command manually scales the example-nodepool to 4 nodes if you want to increase capacity immediately.

Terminal

az aks nodepool scale --resource-group example-resource-group --cluster-name example-aks-cluster --name example-nodepool --node-count 4

Expected Output

Operation "Scale" started for node pool example-nodepool

Succeeded

→

--node-count - Sets the desired number of nodes

This command shows detailed information about the example-nodepool to confirm the current number of nodes and scaling settings.

Terminal

az aks nodepool show --resource-group example-resource-group --cluster-name example-aks-cluster --name example-nodepool

Expected Output

{

  "name": "example-nodepool",

  "count": 4,

  "vmSize": "Standard_DS2_v2",

  "enableAutoScaling": true,

  "minCount": 2,

  "maxCount": 5

}

Key Concept

If you remember nothing else from this pattern, remember: node pools group similar computers and scaling adjusts their number automatically to match your app's needs.

Common Mistakes

Not enabling autoscaling when creating the node pool

The node pool will not adjust size automatically, causing wasted resources or lack of capacity

Always use --enable-cluster-autoscaler with min and max counts to allow scaling

Setting minCount higher than maxCount

This causes configuration errors and prevents scaling from working

Ensure minCount is less than or equal to maxCount

Scaling node pool manually without checking autoscaling settings

Autoscaler may override manual changes or cause conflicts

Check if autoscaling is enabled before manual scaling; disable autoscaling if manual control is needed

Summary

Create a node pool with az aks nodepool add to group similar computers.

Enable autoscaling with min and max counts to adjust node numbers automatically.

Use az aks nodepool list and show to check node pool status and settings.

Scale manually with az aks nodepool scale only if autoscaling is off or needs override.

Practice

1. What is the main purpose of a node pool in an Azure Kubernetes Service (AKS) cluster?

easy

A. To manage user access and permissions

B. To group nodes with similar configurations for easier management

C. To store application data persistently

D. To monitor network traffic between pods

Solution

1. Step 1: Understand node pool concept

   A node pool is a set of machines (nodes) in a cluster that share the same configuration, such as VM size and OS.

2. Step 2: Identify the main purpose

   Grouping nodes with similar settings helps manage and scale them easily within the cluster.

3. Final Answer:

   To group nodes with similar configurations for easier management -> Option B

4. Quick Check:

   Node pool = group of similar nodes [OK]

Hint: Node pools group similar machines in a cluster [OK]

Common Mistakes:

• Confusing node pools with storage or permissions
• Thinking node pools monitor network traffic
• Assuming node pools store data

2. Which of the following is the correct Azure CLI command to scale a node pool named pool1 in an AKS cluster called myCluster to 5 nodes?

easy

A. az aks nodepool scale --resource-group myResourceGroup --cluster-name myCluster --name pool1 --node-count 5

B. az aks scale nodepool --cluster myCluster --name pool1 --count 5

C. az nodepool scale --cluster myCluster --name pool1 --nodes 5

D. az aks nodepool update --resource-group myResourceGroup --cluster myCluster --name pool1 --count 5

Solution

1. Step 1: Recall correct Azure CLI syntax for scaling node pools

   The correct command uses az aks nodepool scale with parameters for resource group, cluster name, node pool name, and node count.

2. Step 2: Match command with options

   az aks nodepool scale --resource-group myResourceGroup --cluster-name myCluster --name pool1 --node-count 5 matches the correct syntax exactly, including all required flags and parameters.

3. Final Answer:

   az aks nodepool scale --resource-group myResourceGroup --cluster-name myCluster --name pool1 --node-count 5 -> Option A

4. Quick Check:

   Correct CLI command = az aks nodepool scale --resource-group myResourceGroup --cluster-name myCluster --name pool1 --node-count 5 [OK]

Hint: Use 'az aks nodepool scale' with correct flags [OK]

Common Mistakes:

• Using wrong command verbs like 'update' or 'scale nodepool'
• Missing resource group or cluster name flags
• Incorrect flag names like --count instead of --node-count

3. Given this YAML snippet for an AKS node pool auto-scaling configuration:

nodePools:
  - name: pool1
    count: 3
    enableAutoScaling: true
    minCount: 2
    maxCount: 6

What is the maximum number of nodes this node pool can scale up to automatically?

medium

A. 6

B. 2

C. 3

D. Unlimited

Solution

1. Step 1: Identify auto-scaling parameters

   The YAML shows enableAutoScaling: true with minCount: 2 and maxCount: 6.

2. Step 2: Understand maxCount meaning

   The maxCount sets the upper limit for automatic scaling, so the node pool can scale up to 6 nodes.

3. Final Answer:

   6 -> Option A

4. Quick Check:

   Max nodes = maxCount = 6 [OK]

Hint: Max nodes = maxCount value in config [OK]

Common Mistakes:

• Confusing current count with maxCount
• Assuming unlimited scaling without maxCount
• Mixing minCount and maxCount values

4. You tried to scale a node pool using this command:
az aks nodepool scale --resource-group myRG --cluster-name myCluster --name poolA --node-count 0
But it failed. What is the most likely reason?

medium

A. Node pool name is case sensitive and must be uppercase

B. Missing --max-count parameter for scaling

C. Node count cannot be set to zero; minimum is 1

D. Cluster name is incorrect

Solution

1. Step 1: Understand node count limits

   AKS node pools require at least one node; zero nodes is invalid and causes failure.

2. Step 2: Check command parameters

   The command tries to scale to zero nodes, which is not allowed, causing the error.

3. Final Answer:

   Node count cannot be set to zero; minimum is 1 -> Option C

4. Quick Check:

   Minimum nodes = 1, zero not allowed [OK]

Hint: Node pools must have at least one node [OK]

Common Mistakes:

• Trying to scale node pool to zero nodes
• Assuming max-count is required for scaling
• Confusing case sensitivity of node pool names

5. You have an AKS cluster with two node pools: pool1 (3 nodes) and pool2 (5 nodes). You want to enable auto-scaling on pool2 to scale between 3 and 10 nodes based on workload. Which of the following steps correctly applies this configuration?

hard

A. Run az aks nodepool update --resource-group RG --cluster-name Cluster --name pool2 --enable-cluster-autoscaler --min-count 3 --max-count 10

B. Run az aks scale nodepool --resource-group RG --cluster Cluster --name pool2 --enable-auto-scaling --min 3 --max 10

C. Run az aks nodepool scale --resource-group RG --cluster-name Cluster --name pool2 --node-count 10

D. Run az aks nodepool update --resource-group RG --cluster-name Cluster --name pool2 --enable-auto-scaling --min-count 3 --max-count 10

Solution

1. Step 1: Identify correct command to enable auto-scaling

   The correct command is az aks nodepool update with flags --enable-auto-scaling, --min-count, and --max-count.

2. Step 2: Compare options for correct flag names and syntax

   Run az aks nodepool update --resource-group RG --cluster-name Cluster --name pool2 --enable-auto-scaling --min-count 3 --max-count 10 uses the correct flag --enable-auto-scaling (not cluster-autoscaler), and proper min/max count flags.

3. Final Answer:

   Run az aks nodepool update --resource-group RG --cluster-name Cluster --name pool2 --enable-auto-scaling --min-count 3 --max-count 10 -> Option D

4. Quick Check:

   Enable auto-scaling with correct flags = Run az aks nodepool update --resource-group RG --cluster-name Cluster --name pool2 --enable-auto-scaling --min-count 3 --max-count 10 [OK]

Hint: Use 'az aks nodepool update' with --enable-auto-scaling flag [OK]

Common Mistakes:

• Using wrong flag --enable-cluster-autoscaler
• Using scale command instead of update for auto-scaling
• Incorrect flag names like --min or --max instead of --min-count and --max-count