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.