Bird
0
0

After upgrading Cluster Autoscaler, you notice nodes are not removed even when underutilized. Which configuration is most likely missing?

medium📝 Troubleshoot Q7 of 15
Kubernetes - Resource Management
After upgrading Cluster Autoscaler, you notice nodes are not removed even when underutilized. Which configuration is most likely missing?
A--balance-similar-node-groups
B--scale-down-enabled=true
C--nodes=1:5:group-b
D--skip-nodes-with-local-storage=false
Step-by-Step Solution
Solution:

  1. Step 1: Identify scale-down enabling flag

    Cluster Autoscaler requires --scale-down-enabled=true to remove underutilized nodes.

  2. Step 2: Understand other flags

    --nodes sets group size, balance flag manages group balancing, skip-nodes flag controls local storage behavior but not scale-down.

  3. Final Answer:

    --scale-down-enabled=true -> Option B

  4. Quick Check:

    Enable scale-down to remove nodes [OK]
Quick Trick: Enable scale-down explicitly to remove nodes [OK]
Common Mistakes:
  • Assuming scale-down is enabled by default
  • Confusing node group size with scale-down
  • Misunderstanding balance flags

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Kubernetes Quizzes
ConfigMaps - Creating ConfigMaps from literals - Quiz 8hard ConfigMaps - Using ConfigMaps as environment variables - Quiz 13medium Ingress - Ingress resource definition - Quiz 8hard Networking - Service mesh concept overview - Quiz 14medium Persistent Storage - Why persistent storage matters in Kubernetes - Quiz 6medium Resource Management - Memory requests and limits - Quiz 10hard Scheduling - DaemonSets for per-node workloads - Quiz 10hard Secrets - External secret management integration - Quiz 2easy Secrets - Using Secrets as environment variables - Quiz 4medium Secrets - Creating Secrets - Quiz 2easy