kubectl describe for details in Kubernetes - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

What does kubectl describe pod mypod show?

You run kubectl describe pod mypod. What kind of information will you see in the output?

A Only the pod's IP address and node name.

B A list of all pods in the cluster with their current status.

C Detailed info about the pod including labels, annotations, container statuses, events, and resource usage.

D The YAML configuration used to create the pod.

💡 Hint

Think about what 'describe' means: it gives detailed info about a specific resource.

kubectl describe shows detailed information about a specific Kubernetes resource. For pods, it includes labels, annotations, container states, events, and more. It does not show just IP or a list of pods or the YAML config.

💻 Command Output

intermediate

What error appears if you describe a non-existent pod?

You run kubectl describe pod unknownpod but the pod does not exist. What is the output?

A Timeout error waiting for pod description

B No output, command silently succeeds

C Syntax error: invalid pod name

D Error from server (NotFound): pods "unknownpod" not found

💡 Hint

If a resource does not exist, kubectl usually reports a NotFound error.

If you try to describe a pod that does not exist, kubectl returns an error message indicating the pod was not found.

❓ Configuration

advanced

Which option shows how to describe all pods in a namespace?

You want to see detailed info for all pods in the namespace dev. Which command will do this?

A kubectl describe all pods dev

B kubectl describe pods -n dev

C kubectl get pods -n dev --describe

D kubectl describe pod dev

💡 Hint

Use plural resource name and specify namespace with -n.

To describe all pods in a namespace, use kubectl describe pods -n dev. The resource name is plural 'pods'.

❓ Troubleshoot

advanced

Why does kubectl describe pod mypod show no events?

You run kubectl describe pod mypod but the events section is empty. What could be a reason?

A No recent events have occurred for the pod.

B The pod is in CrashLoopBackOff state.

C kubectl describe does not show events for pods.

D The pod is running on a node that is offline.

💡 Hint

Events only appear if something happened recently.

If no events appear, it usually means nothing notable happened recently for that pod. Events are transient and may expire.

✅ Best Practice

expert

What is the best way to get detailed info about a pod and save it for later?

You want to describe a pod named mypod and save the detailed output to a file for sharing. Which command is best?

A kubectl describe pod mypod | tee pod-details.txt

B kubectl get pod mypod -o yaml > pod-details.txt

C kubectl logs mypod > pod-details.txt

D kubectl describe pod mypod > pod-details.txt

💡 Hint

You want to see output on screen and save it at the same time.

Using kubectl describe pod mypod | tee pod-details.txt shows the output on screen and saves it to a file simultaneously. Redirecting with > hides output from screen.