Node pools and scaling in Azure - Step-by-Step Execution

Process Flow - Node pools and scaling

Create AKS Cluster

↓

Add Node Pool(s)

↓

Set Node Pool Size

↓

Monitor Load

↓

Scale Node Pool Up or Down

↓

Update Cluster State

This flow shows creating a cluster, adding node pools, setting their size, monitoring load, and scaling node pools accordingly.

Execution Sample

Azure

az aks create --resource-group myRG --name myAKS --node-count 2
az aks nodepool add --resource-group myRG --cluster-name myAKS --name np1 --node-count 3
az aks nodepool scale --resource-group myRG --cluster-name myAKS --name np1 --node-count 5

This code creates an AKS cluster with 2 nodes, adds a node pool with 3 nodes, then scales that node pool to 5 nodes.

Process Table

Step	Action	Node Pool	Node Count Before	Node Count After	Cluster State
1	Create AKS cluster	default	0	2	Cluster with default node pool of 2 nodes
2	Add node pool np1	np1	0	3	Cluster has default (2 nodes) + np1 (3 nodes)
3	Scale node pool np1	np1	3	5	Cluster has default (2 nodes) + np1 (5 nodes)
4	Monitor load	-	-	-	Load monitored, triggers scaling if needed
5	Scale node pool np1 down	np1	5	4	Cluster has default (2 nodes) + np1 (4 nodes)
6	Scale node pool np1 up	np1	4	6	Cluster has default (2 nodes) + np1 (6 nodes)
7	Exit	-	-	-	Scaling complete, cluster stable

💡 Scaling operations complete, cluster node pools adjusted as requested

Status Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 5	After Step 6	Final
default_node_pool_count	0	2	2	2	2	2	2
np1_node_pool_count	0	0	3	5	4	6	6
cluster_total_nodes	0	2	5	7	6	8	8

Key Moments - 3 Insights

Why does the cluster have nodes before adding a new node pool?

Because the default node pool is created with the cluster initially (see Step 1 in execution_table), so nodes exist before adding extra node pools.

What happens if you scale a node pool to a smaller number than before?

The node count decreases accordingly (see Step 5), reducing cluster capacity but keeping the cluster stable.

Does scaling one node pool affect the other node pools?

No, scaling affects only the specified node pool (see Steps 3, 5, 6), other node pools keep their node counts.

Visual Quiz - 3 Questions

Look at the execution_table, what is the node count of node pool 'np1' after Step 3?

A 3

B 2

C 5

D 0

💡 Hint

Check the 'Node Count After' column for Step 3 in execution_table.

At which step does the cluster have a total of 8 nodes?

A Step 5

B Step 6

C Step 3

D Step 2

💡 Hint

Look at 'cluster_total_nodes' in variable_tracker after each step.

If you remove the default node pool, how would the cluster total nodes change after Step 1?

A It would be 0

B It would be 2

C It would be 3

D It would be 5

💡 Hint

Default node pool count is 2 after Step 1; removing it means zero nodes initially.

Concept Snapshot

Node pools are groups of nodes in an AKS cluster.
You can add multiple node pools with different sizes.
Scaling changes the number of nodes in a node pool.
Scaling one node pool does not affect others.
Monitor load to decide when to scale up or down.

Full Transcript

This visual execution shows how an Azure Kubernetes Service (AKS) cluster is created with a default node pool. Then, a new node pool named 'np1' is added with 3 nodes. The node pool 'np1' is scaled up to 5 nodes, then later scaled down and up again. The cluster state updates after each scaling operation. Variables track the number of nodes in each pool and total nodes in the cluster. Key moments clarify that the default node pool exists from the start, scaling affects only the targeted node pool, and scaling down reduces nodes safely. The quiz tests understanding of node counts after steps and effects of removing node pools. The snapshot summarizes node pools and scaling basics in AKS.