Cluster Autoscaler concept in Kubernetes - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

How does Cluster Autoscaler decide to add nodes?

Cluster Autoscaler watches the pods and nodes in a Kubernetes cluster. When does it decide to add new nodes?

A When a node fails health checks repeatedly.

B When CPU usage on existing nodes exceeds 90%.

C When there are pods that cannot be scheduled due to insufficient resources on existing nodes.

D When the number of pods exceeds a fixed threshold regardless of resource availability.

💡 Hint

Think about what causes pods to wait for resources.

Cluster Autoscaler adds nodes only when pods cannot be scheduled because existing nodes lack enough CPU, memory, or other resources.

💻 Command Output

intermediate

Output of Cluster Autoscaler status command

What is the expected output of the command kubectl get deployment cluster-autoscaler -n kube-system -o jsonpath='{.status.availableReplicas}' if the Cluster Autoscaler is running with 1 replica?

A 1

B 0

C null

D Error: deployment not found

💡 Hint

Check the meaning of availableReplicas in deployment status.

The field availableReplicas shows how many pods of the deployment are ready and running. If Cluster Autoscaler is running with 1 pod, it shows 1.

❓ Configuration

advanced

Correct Cluster Autoscaler flag to ignore nodes with specific label

You want Cluster Autoscaler to ignore nodes labeled autoscaler=disabled. Which flag should you add to the Cluster Autoscaler deployment?

A --skip-nodes-with-label=autoscaler=disabled

B --ignore-nodes-with-label=autoscaler=disabled

C --exclude-nodes-with-label=autoscaler=disabled

D --filter-nodes-with-label=autoscaler=disabled

💡 Hint

Check official Cluster Autoscaler flags for ignoring nodes by label.

The correct flag is --skip-nodes-with-label to tell Cluster Autoscaler to ignore nodes with the given label.

❓ Troubleshoot

advanced

Why does Cluster Autoscaler not remove underutilized nodes?

Cluster Autoscaler is running but does not remove nodes even though some nodes have very low CPU and memory usage. What could be a reason?

A Cluster Autoscaler only adds nodes, it never removes nodes.

B There are pods with <code>podDisruptionBudget</code> preventing eviction on those nodes.

C Nodes with low usage are automatically removed by Kubernetes, no need for Cluster Autoscaler.

D Cluster Autoscaler requires manual approval to remove nodes.

💡 Hint

Think about what prevents pods from being moved or deleted.

Pods with podDisruptionBudget can block eviction, so Cluster Autoscaler cannot safely remove nodes hosting those pods.

🔀 Workflow

expert

Order the steps to enable Cluster Autoscaler on a new Kubernetes cluster

Put the steps in the correct order to enable Cluster Autoscaler on a new Kubernetes cluster.

A 1,2,3,4

B 3,1,2,4

C 2,1,3,4

D 1,3,2,4

💡 Hint

Think about what must exist before deploying Cluster Autoscaler and configuring it.

First create the node group, then configure flags, deploy Cluster Autoscaler, and finally verify logs.

Practice

1. What is the primary purpose of the Kubernetes Cluster Autoscaler?

easy

A. Manage pod deployments and replicas

B. Automatically adjust the number of nodes in a cluster based on workload

C. Monitor network traffic between nodes

D. Schedule pods to specific nodes manually

Solution

1. Step 1: Understand Cluster Autoscaler role

   The Cluster Autoscaler watches the cluster workload and adjusts node count automatically.

2. Step 2: Compare with other Kubernetes functions

   Pod management and scheduling are handled by other components, not autoscaler.

3. Final Answer:

   Automatically adjust the number of nodes in a cluster based on workload -> Option B

4. Quick Check:

   Cluster Autoscaler = Adjust nodes automatically [OK]

Hint: Autoscaler changes nodes count, not pods or network [OK]

Common Mistakes:

• Confusing autoscaler with pod scheduler
• Thinking it manages network or pods directly
• Assuming manual node scaling only

2. Which of the following is the correct way to specify the minimum and maximum size of a node group in Cluster Autoscaler configuration?

easy

A. --nodes=5:10:node-group-name

B. --min-nodes=5 --max-nodes=10 --node-group=node-group-name

C. --node-group=node-group-name --nodes=5-10

D. --scale=5,10,node-group-name

Solution

1. Step 1: Recall Cluster Autoscaler node group syntax

   The correct syntax uses --nodes=min:max:node-group-name format.

2. Step 2: Check other options for syntax errors

   Options A, B, and C do not match the documented syntax for Cluster Autoscaler.

3. Final Answer:

   --nodes=5:10:node-group-name -> Option A

4. Quick Check:

   Min:max:group = --nodes option [OK]

Hint: Look for min:max:group format in --nodes option [OK]

Common Mistakes:

• Using separate flags for min and max nodes
• Using commas or dashes incorrectly
• Misplacing node group name

3. Given the following Cluster Autoscaler configuration snippet:

--nodes=2:5:group-a
--nodes=1:3:group-b

What is the maximum number of nodes the autoscaler can add to the cluster?

medium

A. 5 nodes total

B. Cannot determine from this configuration

C. 3 nodes total

D. 8 nodes total

Solution

1. Step 1: Identify max nodes per group

   Group A max nodes = 5, Group B max nodes = 3.

2. Step 2: Sum max nodes for total max

   Total max nodes = 5 + 3 = 8 nodes.

3. Final Answer:

   8 nodes total -> Option D

4. Quick Check:

   Sum max nodes = 8 [OK]

Hint: Add max nodes from all groups for total max [OK]

Common Mistakes:

• Adding min nodes instead of max
• Counting only one group
• Assuming max is fixed cluster size

4. You configured Cluster Autoscaler with:

--nodes=1:4:group-x

But the cluster never scales down nodes even when they are idle. What could be a likely cause?

medium

A. Scale down is disabled or scale down delay is too long

B. Cluster Autoscaler only scales up, not down

C. Minimum nodes is set to 1, so it never removes nodes below that

D. Node group name is incorrect

Solution

1. Step 1: Consider scale-down configuration

   Scale down might be disabled or the scale-down delays (like --scale-down-delay-after-add) are set too long, causing no scale-down even for idle nodes.

2. Step 2: Distinguish from other options

   Min nodes=1 allows scaling down to 1 but not below; incorrect node group would affect scale-up too.

3. Final Answer:

   Scale down is disabled or scale down delay is too long -> Option A

4. Quick Check:

   Disabled scale-down or long delay = no scaling down [OK]

Hint: Check if scale-down is disabled or delay too high [OK]

Common Mistakes:

• Confusing with minimum nodes limit
• Assuming autoscaler can't scale down
• Blaming node group name without checking config

5. You want to optimize costs by configuring Cluster Autoscaler to remove unused nodes quickly but avoid removing nodes that might be needed soon. Which configuration approach is best?

hard

A. Disable scale-down and manually remove nodes

B. Set max nodes equal to min nodes to prevent scaling

C. Set a low scale-down delay and enable scale-down of empty nodes

D. Set a high scale-down delay and disable scale-down of empty nodes

Solution

1. Step 1: Understand scale-down delay and empty node removal

   Low scale-down delay removes unused nodes faster; enabling empty node scale-down helps remove idle nodes.

2. Step 2: Avoid preventing scaling or disabling scale-down

   Setting max = min or disabling scale-down prevents autoscaler from saving costs.

3. Final Answer:

   Set a low scale-down delay and enable scale-down of empty nodes -> Option C

4. Quick Check:

   Fast scale-down + empty node removal = cost optimization [OK]

Hint: Lower delay + empty node scale-down = save costs fast [OK]

Common Mistakes:

• Setting max = min disables scaling
• Disabling scale-down wastes resources
• Using high delay delays cost savings