Why troubleshooting skills are critical in Kubernetes - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the command to check the status of all pods in the default namespace.

Kubernetes

kubectl get [1]

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

Aservices

Bnodes

Cdeployments

Dpods

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'services' instead of 'pods' to check running containers.

The command kubectl get pods lists all pods, which helps to see if they are running or have errors.

2fill in blank

medium

Complete the command to view detailed information about a pod named 'webapp'.

Kubernetes

kubectl describe [1] webapp

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

Apod

Bdeployment

Cnode

Dservice

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'service' or 'deployment' which show different resources.

kubectl describe pod webapp shows detailed info about the pod, including events and status, useful for troubleshooting.

3fill in blank

hard

Fix the error in the command to check logs of a pod named 'backend'.

Kubernetes

kubectl logs [1] backend

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

Anode

Bservice

Cpod

Ddeployment

Attempts:

3 left

💡 Hint

Common Mistakes

Trying to get logs from 'service' or 'deployment' which is invalid.

The correct resource type for logs is pod. Using other types causes errors.

4fill in blank

hard

Fill both blanks to create a command that lists pods with their status in all namespaces.

Kubernetes

kubectl get [1] --all-[2]

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

Apods

Bservices

Cnamespaces

Dnodes

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'services' or 'nodes' instead of 'pods'.

kubectl get pods --all-namespaces lists all pods across every namespace, showing their status for troubleshooting.

5fill in blank

hard

Fill all three blanks to create a command that filters pods with status 'CrashLoopBackOff' in the 'prod' namespace.

Kubernetes

kubectl get [1] -n [2] | grep [3]

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

Apods

Bprod

CRunning

DCrashLoopBackOff

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'Running' instead of 'CrashLoopBackOff' for filtering.

kubectl get pods -n prod | grep CrashLoopBackOff lists pods in the 'prod' namespace and filters those with 'CrashLoopBackOff' status, helping identify failing pods.