Node pools and auto scaling in GCP - Commands & Configuration

Introduction

When you run apps on Google Kubernetes Engine, you need groups of machines called node pools. Auto scaling helps these groups grow or shrink automatically based on how busy your app is. This saves money and keeps your app running smoothly.

When your app traffic changes a lot during the day and you want to save costs by using fewer machines when traffic is low.

When you want to add different types of machines for special tasks, like some with more memory or CPUs.

When you want Google Cloud to automatically add or remove machines so your app stays fast without manual work.

When you want to test how your app behaves with different numbers of machines.

When you want to keep your app available even if some machines fail by having extra machines ready.

Commands

This command creates a new node pool named 'example-pool' with 3 machines of type e2-medium in the 'example-cluster'. We specify the region to place the machines close to users.

Terminal

gcloud container node-pools create example-pool --cluster example-cluster --num-nodes 3 --machine-type e2-medium --region us-central1

Expected Output

Created [https://container.googleapis.com/v1/projects/my-project/locations/us-central1/clusters/example-cluster/nodePools/example-pool].

→

--num-nodes - Sets the initial number of machines in the node pool

→

--machine-type - Specifies the type of machine for nodes

→

--region - Defines the region where the cluster and nodes are created

This command enables auto scaling on the 'example-pool' node pool in the 'example-cluster'. It allows the pool to have between 1 and 5 machines depending on workload.

Terminal

gcloud container clusters update example-cluster --region us-central1 --enable-autoscaling --min-nodes 1 --max-nodes 5 --node-pool example-pool

Expected Output

Updated [https://container.googleapis.com/v1/projects/my-project/locations/us-central1/clusters/example-cluster].

→

--enable-autoscaling - Turns on auto scaling for the node pool

→

--min-nodes - Sets the minimum number of nodes to keep running

→

--max-nodes - Sets the maximum number of nodes allowed

→

--node-pool - Specifies which node pool to enable autoscaling on

This command lists all node pools in the 'example-cluster' so you can check their status and settings.

Terminal

gcloud container node-pools list --cluster example-cluster --region us-central1

Expected Output

NAME           STATUS   MACHINE_TYPE   NODE_VERSION   AUTOSCALING   MIN_NODES   MAX_NODES

example-pool   RUNNING  e2-medium     1.26.3-gke.100  ENABLED      1           5

This command shows all the machines (nodes) currently running in your Kubernetes cluster so you can see how many are active.

Terminal

kubectl get nodes

Expected Output

NAME                                       STATUS   ROLES    AGE   VERSION

example-pool-abc123-xyz                     Ready    <none>   10m   v1.26.3-gke.100

example-pool-def456-uvw                     Ready    <none>   10m   v1.26.3-gke.100

example-pool-ghi789-rst                     Ready    <none>   10m   v1.26.3-gke.100

Key Concept

If you remember nothing else from this pattern, remember: node pools group machines with similar settings, and auto scaling lets Google add or remove these machines automatically based on your app's needs.

Common Mistakes

Not enabling auto scaling after creating the node pool

The node pool will stay at the fixed number of nodes and won't adjust to workload changes, wasting resources or causing slowdowns.

Always run the update command with --enable-autoscaling and set min and max nodes to allow scaling.

Setting min-nodes higher than max-nodes

This causes an error because the minimum number of nodes cannot be greater than the maximum.

Ensure min-nodes is less than or equal to max-nodes when enabling auto scaling.

Forgetting to specify the correct region or cluster name

Commands will fail or apply changes to the wrong cluster, causing confusion or errors.

Double-check the cluster name and region flags in every command.

Summary

Create a node pool to group similar machines for your Kubernetes cluster.

Enable auto scaling on the node pool to let Google add or remove machines automatically.

Use commands to check node pool settings and see active machines in your cluster.

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