Metrics Server installation in Kubernetes - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the command to install Metrics Server using kubectl.

Kubernetes

kubectl apply -f [1]

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

Ahttps://github.com/kubernetes-sigs/metrics-server/releases/latest/download/components.yaml

Bmetrics-server.yaml

Cdeployment.yaml

Dservice.yaml

Attempts:

3 left

💡 Hint

Common Mistakes

Using a local file name instead of the official URL.

Applying only service.yaml or deployment.yaml which are incomplete manifests.

The correct command applies the official Metrics Server components manifest from the GitHub release URL.

2fill in blank

medium

Complete the kubectl command to check if Metrics Server pods are running in the kube-system namespace.

Kubernetes

kubectl get pods -n [1]

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

Adefault

Bmonitoring

Cmetrics

Dkube-system

Attempts:

3 left

💡 Hint

Common Mistakes

Checking pods in the default namespace where Metrics Server is not deployed.

Using a non-existent namespace like 'metrics' or 'monitoring'.

Metrics Server runs in the kube-system namespace, so you check pods there.

3fill in blank

hard

Fix the error in the Metrics Server deployment by completing the args to allow insecure TLS communication.

Kubernetes

- --kubelet-insecure-tls=[1]

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

Atrue

Bfalse

Cyes

Dno

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'false' disables insecure TLS, causing connection errors.

Using 'yes' or 'no' are invalid boolean values for this flag.

Setting --kubelet-insecure-tls=true allows Metrics Server to skip TLS verification when connecting to kubelets.

4fill in blank

hard

Fill both blanks to complete the command that checks Metrics Server API availability.

Kubernetes

kubectl top [1] -n [2]

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

Anodes

Bpods

Ckube-system

Ddefault

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'pods' with 'default' namespace which may not show Metrics Server data.

Mixing nodes with kube-system namespace which is not required.

The command kubectl top nodes -n default checks resource usage of nodes via Metrics Server. The kubectl top nodes command does not require specifying the kube-system namespace because nodes are cluster-wide resources.

5fill in blank

hard

Fill all three blanks to create a label selector command to find Metrics Server pods.

Kubernetes

kubectl get pods -n [1] -l [2]=[3]

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

Akube-system

Bk8s-app

Cmetrics-server

Ddefault

Attempts:

3 left

💡 Hint

Common Mistakes

Using the wrong namespace like 'default'.

Using incorrect label keys or values.

This command lists pods in the kube-system namespace with label k8s-app=metrics-server, which identifies Metrics Server pods.