Node pools and auto scaling in GCP - Mini Project: Build & Apply

Node Pools and Auto Scaling in GCP

📖 Scenario: You are managing a Google Kubernetes Engine (GKE) cluster for a small company. The company wants to organize their cluster nodes into groups called node pools. Each node pool can have different machine types and settings. They also want the cluster to automatically add or remove nodes based on the workload to save costs and keep performance good.

🎯 Goal: Build a GKE cluster configuration with two node pools and enable auto scaling on one of the node pools.

📋 What You'll Learn

Create a GKE cluster named my-gke-cluster in the us-central1 region

Add a node pool named default-pool with machine type e2-medium and 3 nodes

Add a second node pool named autoscale-pool with machine type e2-small and 1 node

Enable auto scaling on the autoscale-pool with minimum 1 node and maximum 5 nodes

💡 Why This Matters

🌍 Real World

Organizing nodes into pools and enabling auto scaling helps companies manage cloud resources efficiently, saving money and improving performance.

💼 Career

Cloud engineers and DevOps professionals often configure node pools and auto scaling to optimize Kubernetes clusters in production.

1

Create the initial GKE cluster configuration

Create a variable called cluster_config as a dictionary with the key name set to "my-gke-cluster" and the key location set to "us-central1".

GCP

# Your code here

Hint

Think of cluster_config as a map that holds the cluster's name and location.

2

Add the default node pool configuration

Add a key node_pools to cluster_config with a list containing one dictionary. This dictionary should have name set to "default-pool", machine_type set to "e2-medium", and initial_node_count set to 3.

GCP

cluster_config = {
    "name": "my-gke-cluster",
    "location": "us-central1"
}
# Add node_pools key with default-pool configuration below
# Your code here

Hint

Remember, node_pools is a list of dictionaries, each describing a node pool.

3

Add the autoscale node pool configuration

Append a dictionary to the node_pools list in cluster_config with name set to "autoscale-pool", machine_type set to "e2-small", initial_node_count set to 1, and add an autoscaling key with a dictionary value containing min_node_count set to 1 and max_node_count set to 5.

GCP

cluster_config = {
    "name": "my-gke-cluster",
    "location": "us-central1",
    "node_pools": [
        {
            "name": "default-pool",
            "machine_type": "e2-medium",
            "initial_node_count": 3
        }
    ]
}
# Append autoscale-pool configuration below
# Your code here

Hint

Auto scaling settings go inside the autoscaling dictionary inside the node pool.

4

Complete the cluster configuration with auto scaling enabled

Ensure the cluster_config dictionary includes both node pools with their settings and auto scaling enabled on autoscale-pool. The final structure should have name, location, and node_pools keys with the correct nested dictionaries and lists as described.

GCP

cluster_config = {
    "name": "my-gke-cluster",
    "location": "us-central1",
    "node_pools": [
        {
            "name": "default-pool",
            "machine_type": "e2-medium",
            "initial_node_count": 3
        },
        {
            "name": "autoscale-pool",
            "machine_type": "e2-small",
            "initial_node_count": 1,
            "autoscaling": {
                "min_node_count": 1,
                "max_node_count": 5
            }
        }
    ]
}
# Confirm the cluster_config structure is complete
# Your code here

Hint

Review the entire cluster_config dictionary to ensure all parts are included correctly.

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