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.

Practice

1. What does the kubectl describe command primarily show about a Kubernetes resource?

easy

A. Detailed information including status, events, and configuration of the resource

B. Only the YAML configuration of the resource

C. The logs generated by the resource

D. The list of all resources in the cluster

Solution

1. Step 1: Understand the purpose of kubectl describe

   This command provides detailed information about a specific Kubernetes resource, including its current status, configuration details, and recent events.

2. Step 2: Compare with other kubectl commands

   Unlike kubectl get which lists resources or kubectl logs which shows logs, kubectl describe gives a detailed snapshot of the resource's state and events.

3. Final Answer:

   Detailed information including status, events, and configuration of the resource -> Option A

4. Quick Check:

   kubectl describe = detailed resource info [OK]

Hint: Remember: describe = detailed info + events [OK]

Common Mistakes:

• Confusing describe with get for YAML output
• Expecting logs from describe command
• Using describe without specifying resource name

2. Which of the following is the correct syntax to describe a pod named web-server in the default namespace?

easy

A. kubectl describe pod web-server -n default

B. kubectl describe pods web-server default

C. kubectl describe web-server pod -n default

D. kubectl describe pod web-server

Solution

1. Step 1: Identify correct resource type and name syntax

   The command format is kubectl describe <resource-type> <resource-name>. For pods, resource type is pod (singular or plural works but singular is preferred).

2. Step 2: Specify namespace correctly

   To specify the namespace, use the -n or --namespace flag after the resource name. The correct placement is kubectl describe pod web-server -n default.

3. Final Answer:

   kubectl describe pod web-server -n default -> Option A

4. Quick Check:

   Correct syntax = resource type + name + -n namespace [OK]

Hint: Use '-n' flag for namespace after resource name [OK]

Common Mistakes:

• Placing namespace as a positional argument
• Swapping resource name and type order
• Omitting the namespace flag when needed

3. Given the command kubectl describe node worker-node-1, what key information would you expect to see in the output?

medium

A. List of all pods in the cluster

B. Pod logs running on worker-node-1

C. Detailed node status including capacity, conditions, and allocated resources

D. YAML configuration of the node

Solution

1. Step 1: Understand what describing a node shows

   kubectl describe node shows detailed info about the node's status, including CPU and memory capacity, conditions like Ready or NotReady, and resource allocation.

2. Step 2: Differentiate from other outputs

   It does not show pod logs (that's kubectl logs), nor does it list all pods or show YAML (that's kubectl get node -o yaml).

3. Final Answer:

   Detailed node status including capacity, conditions, and allocated resources -> Option C

4. Quick Check:

   Describe node = status + capacity + conditions [OK]

Hint: Describe node shows status and capacity, not logs [OK]

Common Mistakes:

• Expecting pod logs from node describe
• Confusing describe output with get -o yaml
• Thinking it lists all pods in cluster

4. You run kubectl describe pod myapp-pod but get an error: Error from server (NotFound): pods "myapp-pod" not found. What is the most likely cause?

medium

A. You need to add --all-namespaces to describe pods

B. The kubectl describe command does not support pods

C. The Kubernetes cluster is down

D. The pod name is incorrect or does not exist in the current namespace

Solution

1. Step 1: Analyze the error message

   The error says the pod "myapp-pod" was not found. This usually means the pod name is wrong or it does not exist in the current namespace.

2. Step 2: Check command and cluster status

   kubectl describe supports pods, and the cluster being down would cause different errors. Also, --all-namespaces is not required but can help find pods in other namespaces.

3. Final Answer:

   The pod name is incorrect or does not exist in the current namespace -> Option D

4. Quick Check:

   NotFound error = wrong pod name or namespace [OK]

Hint: Check pod name and namespace if NotFound error appears [OK]

Common Mistakes:

• Assuming describe doesn't support pods
• Ignoring namespace context
• Thinking cluster is down without checking

5. You want to check why a deployment named frontend is not creating pods as expected. Which kubectl describe command and output section will help you diagnose the issue?

hard

A. kubectl describe pod frontend; check the Status section for pod readiness

B. kubectl describe deployment frontend; check the Events section for errors

C. kubectl describe service frontend; check the Endpoints section

D. kubectl describe node frontend; check the Capacity section

Solution

1. Step 1: Identify the correct resource to describe

   Since the issue is with a deployment named frontend, you should describe the deployment resource, not pods, services, or nodes.

2. Step 2: Locate the useful output section

   The Events section in the deployment description shows recent errors or warnings related to pod creation or scaling issues, which helps diagnose why pods are not created.

3. Final Answer:

   kubectl describe deployment frontend; check the Events section for errors -> Option B

4. Quick Check:

   Describe deployment + Events = diagnose pod creation issues [OK]

Hint: Check deployment Events for pod creation errors [OK]

Common Mistakes:

• Describing pod instead of deployment
• Checking service or node instead of deployment
• Ignoring Events section in output