Node pools and auto scaling in GCP - Step-by-Step Execution

Process Flow - Node pools and auto scaling

Create Node Pool

↓

Set Min and Max Nodes

↓

Monitor Cluster Load

↓

Is Load High?

No→Keep Current Nodes

Yes↓

Scale Up Nodes

↓

Is Load Low?

No→Keep Current Nodes

Yes↓

Scale Down Nodes

↓

Repeat Monitoring

This flow shows how a node pool is created with min and max nodes, then the system monitors load and scales nodes up or down automatically.

Execution Sample

GCP

gcloud container node-pools create pool-1 --cluster=my-cluster --num-nodes=3 --enable-autoscaling --min-nodes=1 --max-nodes=5

# Cluster load increases
# Autoscaler adds nodes

# Cluster load decreases
# Autoscaler removes nodes

This code creates a node pool with autoscaling enabled, then nodes are added or removed based on cluster load.

Process Table

Step	Cluster Load	Current Nodes	Autoscaler Decision	Action Taken
1	Low	3	No scaling needed	Nodes remain 3
2	High	3	Scale up	Nodes increased to 4
3	High	4	Scale up	Nodes increased to 5
4	High	5	Max nodes reached	Nodes remain 5
5	Medium	5	No scaling needed	Nodes remain 5
6	Low	5	Scale down	Nodes decreased to 4
7	Low	4	Scale down	Nodes decreased to 3
8	Low	3	Scale down	Nodes decreased to 2
9	Low	2	Scale down	Nodes decreased to 1
10	Low	1	Min nodes reached	Nodes remain 1

💡 Autoscaler stops scaling when min or max node limits are reached

Status Tracker

Variable	Start	After 1	After 2	After 3	After 4	After 5	After 6	After 7	After 8	After 9	Final
Cluster Load	Low	High	High	High	Medium	Low	Low	Low	Low	Low	Low
Current Nodes	3	3	4	5	5	5	4	3	2	1	1
Autoscaler Decision	No scaling	Scale up	Scale up	Max nodes	No scaling	Scale down	Scale down	Scale down	Scale down	Min nodes	Min nodes

Key Moments - 3 Insights

Why does the autoscaler stop adding nodes at step 4 even though the load is high?

At step 4, the autoscaler reached the maximum node limit (5 nodes), so it cannot add more nodes despite high load, as shown in the execution_table row 4.

Why does the autoscaler not reduce nodes below 1 at step 10?

The autoscaler respects the minimum node limit (1 node), so it stops scaling down at step 10, as seen in execution_table row 10.

What happens if the cluster load stays medium at step 5?

When load is medium, autoscaler decides no scaling is needed, so nodes remain the same, as shown in execution_table row 5.

Visual Quiz - 3 Questions

Look at the execution_table, how many nodes are running after step 3?

A 3 nodes

B 4 nodes

C 5 nodes

D 6 nodes

💡 Hint

Check the 'Current Nodes' column at step 3 in the execution_table.

At which step does the autoscaler first scale down nodes?

A Step 6

B Step 4

C Step 5

D Step 7

💡 Hint

Look for the first 'Scale down' decision in the 'Autoscaler Decision' column.

If the minimum nodes were set to 2 instead of 1, what would be the node count at step 10?

A 1 node

B 2 nodes

C 3 nodes

D 0 nodes

💡 Hint

Refer to the 'Min nodes reached' logic in the execution_table and variable_tracker.

Concept Snapshot

Node pools group worker machines in a cluster.
Autoscaling adjusts node count based on load.
Set minimum and maximum nodes to control scaling.
Autoscaler adds nodes when load is high.
Autoscaler removes nodes when load is low.
Scaling stops at min or max node limits.

Full Transcript

Node pools are groups of worker machines in a cloud cluster. You create a node pool and set minimum and maximum nodes to control autoscaling. The system watches the cluster load. If load is high, it adds nodes up to the maximum limit. If load is low, it removes nodes down to the minimum limit. This process repeats to keep resources efficient. Autoscaling stops adding nodes when max nodes are reached and stops removing nodes when min nodes are reached.

Practice

1. What is the main purpose of a node pool in a GKE cluster?

easy

A. To group similar machines for easier management and scaling

B. To store data permanently in the cluster

C. To monitor network traffic between nodes

D. To create backups of the cluster configuration

Solution

1. Step 1: Understand node pool concept

   A node pool is a set of nodes with the same configuration in a cluster.

2. Step 2: Identify node pool purpose

   Node pools help manage and scale groups of similar machines easily.

3. Final Answer:

   To group similar machines for easier management and scaling -> Option A

4. Quick Check:

   Node pool = group similar machines [OK]

Hint: Node pools group similar nodes for scaling and management [OK]

Common Mistakes:

• Confusing node pools with storage or backup features
• Thinking node pools monitor network traffic
• Assuming node pools store data permanently

2. Which of the following is the correct way to enable auto scaling on a node pool using gcloud CLI?

easy

A. gcloud container clusters create CLUSTER_NAME --autoscaling

B. gcloud container node-pools update POOL_NAME --enable-autoscaling --min-nodes=1 --max-nodes=5

C. gcloud container node-pools create POOL_NAME --autoscaling-enabled

D. gcloud container node-pools set-autoscale POOL_NAME --min=1 --max=5

Solution

1. Step 1: Recall gcloud syntax for node pool auto scaling

   The correct command uses 'node-pools update' with '--enable-autoscaling' and min/max nodes.

2. Step 2: Match options with correct syntax

   gcloud container node-pools update POOL_NAME --enable-autoscaling --min-nodes=1 --max-nodes=5 matches the correct syntax and flags for enabling auto scaling.

3. Final Answer:

   gcloud container node-pools update POOL_NAME --enable-autoscaling --min-nodes=1 --max-nodes=5 -> Option B

4. Quick Check:

   Enable autoscaling with update and min/max nodes [OK]

Hint: Use 'node-pools update' with --enable-autoscaling and min/max nodes [OK]

Common Mistakes:

• Using cluster create command to enable node pool autoscaling
• Incorrect flag names like --autoscaling-enabled
• Commands that do not specify min and max nodes

3. Given a node pool with auto scaling enabled (min nodes=2, max nodes=4), what happens when workload increases beyond current capacity?

medium

A. The node pool scales up by adding nodes up to the max limit

B. The node pool scales down to reduce costs

C. The cluster deletes existing nodes to balance load

D. The workload is rejected until manual scaling is done

Solution

1. Step 1: Understand auto scaling behavior on workload increase

   Auto scaling adds nodes when workload exceeds current capacity, up to max nodes.

2. Step 2: Analyze options

   The node pool scales up by adding nodes up to the max limit correctly describes scaling up; others describe incorrect or opposite behaviors.

3. Final Answer:

   The node pool scales up by adding nodes up to the max limit -> Option A

4. Quick Check:

   Workload increase triggers scale up [OK]

Hint: Auto scaling adds nodes when workload grows, up to max nodes [OK]

Common Mistakes:

• Thinking auto scaling scales down on workload increase
• Assuming nodes are deleted to balance load
• Believing workload is rejected without manual scaling

4. You configured auto scaling on a node pool but notice nodes are not scaling up despite high CPU usage. What is the most likely cause?

medium

A. Auto scaling is disabled on the node pool

B. The node pool has no nodes initially

C. The cluster is in maintenance mode

D. The max nodes limit is set too low

Solution

1. Step 1: Check auto scaling settings

   If auto scaling is enabled but nodes don't increase, max nodes limit may be reached.

2. Step 2: Identify cause of no scale up

   The max nodes limit is set too low explains that max nodes limit is too low to add more nodes despite workload.

3. Final Answer:

   The max nodes limit is set too low -> Option D

4. Quick Check:

   Max nodes limit blocks scaling up [OK]

Hint: Check max nodes limit if scaling doesn't happen [OK]

Common Mistakes:

• Assuming auto scaling is disabled without checking limits
• Ignoring max nodes limit as a cause
• Thinking cluster maintenance mode blocks scaling always

5. You want to optimize costs by using multiple node pools with different machine types and enable auto scaling only on the pool handling variable workloads. Which approach is best?

hard

A. Disable auto scaling on all node pools and manually adjust nodes daily

B. Use a single node pool with auto scaling enabled for all workloads

C. Create a small fixed node pool for stable workloads and a separate auto scaling node pool for variable workloads

D. Create multiple auto scaling node pools with the same machine type

Solution

1. Step 1: Understand workload types and node pools

   Stable workloads benefit from fixed nodes; variable workloads benefit from auto scaling.

2. Step 2: Choose best cost optimization strategy

   Create a small fixed node pool for stable workloads and a separate auto scaling node pool for variable workloads separates stable and variable workloads into different pools with appropriate scaling.

3. Final Answer:

   Create a small fixed node pool for stable workloads and a separate auto scaling node pool for variable workloads -> Option C

4. Quick Check:

   Separate pools for stable and variable workloads optimize cost [OK]

Hint: Use fixed pool for stable, auto scaling pool for variable workloads [OK]

Common Mistakes:

• Using single auto scaling pool for all workloads
• Disabling auto scaling and relying on manual scaling
• Creating multiple auto scaling pools with same machine type unnecessarily