Cluster Autoscaler concept in Kubernetes - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to specify the Cluster Autoscaler deployment namespace.

Kubernetes

kubectl apply -f cluster-autoscaler.yaml -n [1]

Drag options to blanks, or click blank then click option'

Akube-system

Bdefault

Cautoscaler

Dmonitoring

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'default' namespace instead of 'kube-system'.

Choosing a non-existent namespace.

The Cluster Autoscaler usually runs in the kube-system namespace where core Kubernetes components reside.

2fill in blank

medium

Complete the command to check the Cluster Autoscaler logs.

Kubernetes

kubectl logs deployment/cluster-autoscaler -n kube-system -c [1]

Drag options to blanks, or click blank then click option'

Aautoscaler

Bmain

Cca-container

Dcluster-autoscaler

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect container names like 'autoscaler' or 'main'.

The container name in the Cluster Autoscaler deployment is usually cluster-autoscaler.

3fill in blank

hard

Fix the error in the Cluster Autoscaler command to scale nodes automatically.

Kubernetes

kubectl autoscale deployment my-app --min=[1] --max=5 --cpu-percent=80

Drag options to blanks, or click blank then click option'

A3

B0

C1

D5

Attempts:

3 left

💡 Hint

Common Mistakes

Setting minimum nodes to zero causes errors.

Setting minimum nodes higher than maximum.

The minimum number of nodes must be at least 1 to allow scaling up from zero.

4fill in blank

hard

Fill both blanks to create a node group autoscaling configuration snippet.

Kubernetes

"""
apiVersion: autoscaling.k8s.io/v1
kind: ClusterAutoscaler
metadata:
  name: cluster-autoscaler
spec:
  scaleDown:
    enabled: [1]
    delayAfterAdd: [2]
"""

Drag options to blanks, or click blank then click option'

Atrue

Bfalse

C10m

D5m

Attempts:

3 left

💡 Hint

Common Mistakes

Disabling scale down by setting it to false.

Setting delayAfterAdd too low causing nodes to be removed too quickly.

Scale down should be enabled (true) and delay after adding nodes is commonly set to 10m to avoid premature scale down.

5fill in blank

hard

Fill all three blanks to complete the Cluster Autoscaler deployment container args.

Kubernetes

"""
containers:
- name: cluster-autoscaler
  image: k8s.gcr.io/autoscaling/cluster-autoscaler:v1.22.0
  command:
  - ./cluster-autoscaler
  - --v=4
  - --cloud-provider=[1]
  - --nodes=[2]:[3]:node-group-1
"""

Drag options to blanks, or click blank then click option'

Aaws

B1

C5

Dgcp

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong cloud provider name.

Setting minimum nodes higher than maximum nodes.

The cloud provider is gcp for Google Cloud. The node group has a minimum of 1 and maximum of 5 nodes.

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