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.

Practice

1. Why is troubleshooting important in Kubernetes environments?

easy

A. It helps keep applications running smoothly and reduces downtime.

B. It allows you to write new Kubernetes features.

C. It is only needed when setting up the cluster.

D. It replaces the need for monitoring tools.

Solution

1. Step 1: Understand the role of troubleshooting

   Troubleshooting helps identify and fix problems to keep apps healthy.

2. Step 2: Connect troubleshooting to app availability

   Fixing issues quickly reduces downtime and keeps services available.

3. Final Answer:

   It helps keep applications running smoothly and reduces downtime. -> Option A

4. Quick Check:

   Troubleshooting = Keeps apps healthy [OK]

Hint: Troubleshooting = Fix problems fast to avoid downtime [OK]

Common Mistakes:

• Thinking troubleshooting is only for setup
• Confusing troubleshooting with feature development
• Believing monitoring replaces troubleshooting

2. Which kubectl command is used to view detailed information about a pod, including events and status?

easy

A. kubectl get pod <pod-name>

B. kubectl exec <pod-name> -- ls

C. kubectl logs <pod-name>

D. kubectl describe pod <pod-name>

Solution

1. Step 1: Identify command purpose

   kubectl describe pod shows detailed info including events and status.

2. Step 2: Compare with other commands

   get shows summary, logs shows output logs, exec runs commands inside pod.

3. Final Answer:

   kubectl describe pod <pod-name> -> Option D

4. Quick Check:

   Describe = detailed pod info [OK]

Hint: Describe shows detailed pod info, not just summary [OK]

Common Mistakes:

• Using get instead of describe for details
• Confusing logs with describe output
• Using exec to view pod info

3. What will be the output of the command kubectl logs myapp-pod if the pod is running a web server that just started successfully?

medium

A. Server started on port 8080

B. No logs available

C. Error: pod not found

D. kubectl command not recognized

Solution

1. Step 1: Understand kubectl logs output

   This command shows the output logs from the container in the pod.

2. Step 2: Match expected logs for a running web server

   A successful start usually logs a message like "Server started on port 8080".

3. Final Answer:

   Server started on port 8080 -> Option A

4. Quick Check:

   Logs show server start message [OK]

Hint: Logs show what the app prints, like startup messages [OK]

Common Mistakes:

• Expecting error when pod exists and runs
• Thinking logs are empty if no errors
• Confusing command errors with app logs

4. You run kubectl get pods and see your pod stuck in CrashLoopBackOff. What is the best first step to troubleshoot?

medium

A. Delete the pod immediately

B. Check pod logs with kubectl logs <pod-name>

C. Restart the Kubernetes cluster

D. Run kubectl exec <pod-name> -- ls without checking logs

Solution

1. Step 1: Identify the problem state

   CrashLoopBackOff means the pod keeps crashing and restarting.

2. Step 2: Use logs to find crash cause

   Checking logs with kubectl logs helps find error messages causing crashes.

3. Final Answer:

   Check pod logs with kubectl logs <pod-name> -> Option B

4. Quick Check:

   CrashLoopBackOff? Check logs first [OK]

Hint: Logs reveal crash reasons before deleting or restarting [OK]

Common Mistakes:

• Deleting pod without checking cause
• Restarting cluster too soon
• Running exec blindly without logs

5. A Kubernetes deployment is not updating pods after you apply a new image version. Which troubleshooting steps should you take to find the root cause?

hard

A. Restart the kubelet service on all nodes.

B. Immediately delete all pods to force recreation.

C. Check deployment status with kubectl rollout status deployment/<name> and describe the deployment.

D. Run kubectl exec on pods to manually update the image.

Solution

1. Step 1: Verify rollout status

   Use kubectl rollout status to check if deployment is progressing or stuck.

2. Step 2: Describe deployment for events and errors

   kubectl describe deployment shows events like image pull errors or update failures.

3. Final Answer:

   Check deployment status with kubectl rollout status deployment/<name> and describe the deployment. -> Option C

4. Quick Check:

   Rollout status + describe = find update issues [OK]

Hint: Check rollout status and describe deployment first [OK]

Common Mistakes:

• Deleting pods without understanding cause
• Restarting kubelet without evidence
• Trying to update image inside pods manually