Node pools and auto scaling in GCP - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a node pool in Google Kubernetes Engine (GKE)?

A node pool is a group of nodes within a GKE cluster that share the same configuration, such as machine type and labels. It allows you to manage and scale sets of nodes independently.

beginner

How does auto scaling work in GKE node pools?

Auto scaling automatically adjusts the number of nodes in a node pool based on the workload demand. It adds nodes when more resources are needed and removes nodes when demand decreases.

intermediate

Why use multiple node pools in a GKE cluster?

Using multiple node pools lets you run different types of workloads with different machine types or configurations. For example, one pool for CPU-intensive tasks and another for memory-intensive tasks.

intermediate

What is the difference between cluster autoscaler and horizontal pod autoscaler?

Cluster autoscaler adjusts the number of nodes in the cluster (node pools), while horizontal pod autoscaler adjusts the number of pods (containers) running inside the cluster based on CPU or custom metrics.

beginner

What happens if auto scaling is disabled on a node pool?

If auto scaling is disabled, the node pool size stays fixed. You must manually add or remove nodes, which can lead to wasted resources or insufficient capacity during workload changes.

What does a node pool in GKE represent?

A A group of nodes with the same configuration

B A single pod running in the cluster

C A storage bucket for logs

D A network firewall rule

A node pool is a set of nodes with the same machine type and settings in a GKE cluster.

What triggers the cluster autoscaler to add nodes?

A When a pod is deleted

B When pods need more resources than current nodes provide

C When a new node pool is created

D When the cluster is idle

The cluster autoscaler adds nodes when pods cannot be scheduled due to lack of resources.

Which of these is NOT a benefit of using multiple node pools?

A Automatically scaling pods inside nodes

B Isolating workloads for security or compliance

C Running different workloads with optimized resources

D Using different machine types in the same cluster

Scaling pods is done by horizontal pod autoscaler, not by node pools.

If auto scaling is disabled, what must you do to change node count?

A Delete the node pool

B Wait for automatic scaling

C Restart the cluster

D Manually add or remove nodes

Without auto scaling, node count changes require manual intervention.

What is the main difference between cluster autoscaler and horizontal pod autoscaler?

A Both scale nodes only

B Cluster autoscaler changes pods; pod autoscaler changes nodes

C Cluster autoscaler changes nodes; pod autoscaler changes pods

D Both scale pods only

Cluster autoscaler adjusts node count; horizontal pod autoscaler adjusts pod count.

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

Think about how you organize workers with similar tools for specific tasks.

Describe how auto scaling works for node pools and why it helps manage resources.

Imagine a restaurant adding or removing tables depending on how many customers arrive.