Node pools and scaling in Azure - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a node pool in Azure Kubernetes Service (AKS)?

A node pool is a group of virtual machines with the same configuration within an AKS cluster. It allows you to manage and scale sets of nodes independently.

beginner

How does scaling work with node pools in AKS?

You can increase or decrease the number of nodes in a node pool to match workload demands. This can be done manually or automatically using the cluster autoscaler.

intermediate

Why use multiple node pools in an AKS cluster?

Multiple node pools let you run different types of workloads with different VM sizes or OS types, improving resource use and cost efficiency.

beginner

What is the benefit of enabling autoscaling on a node pool?

Autoscaling automatically adjusts the number of nodes based on workload, helping maintain performance while controlling costs.

intermediate

Can you change the VM size of a node pool after creation in AKS?

No, you cannot change the VM size of an existing node pool. Instead, you create a new node pool with the desired size and migrate workloads.

What does a node pool in AKS consist of?

A A network security group

B A group of identical virtual machines

C A storage account

D A single container instance

A node pool is a group of virtual machines with the same configuration running in an AKS cluster.

How can you scale a node pool in AKS?

A By changing the cluster region

B By changing the VM size directly

C By modifying the container image

D By increasing or decreasing the number of nodes

Scaling a node pool means adjusting the number of nodes to meet workload demands.

What is a key advantage of using multiple node pools?

A Increasing storage capacity automatically

B Reducing the number of clusters

C Running different workloads with different VM types

D Changing the Kubernetes version

Multiple node pools allow different VM sizes or OS types for different workloads.

What does autoscaling do in an AKS node pool?

A Automatically adjusts node count based on workload

B Automatically updates Kubernetes version

C Automatically changes VM size

D Automatically backs up data

Autoscaling changes the number of nodes automatically to match workload needs.

If you want to use a different VM size for your node pool, what should you do?

A Create a new node pool with the desired VM size

B Change the container image

C Resize the existing node pool VM size

D Restart the cluster

VM size cannot be changed on an existing node pool; create a new one instead.

Explain what a node pool is and why it is useful in AKS.

Think about how you group similar workers to handle tasks efficiently.

Describe how scaling works with node pools and the benefits of autoscaling.

Consider how you add or remove workers based on how busy you are.

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