Viewing Pod details and logs in Kubernetes - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Viewing logs of a specific container in a multi-container Pod

You have a Pod named webapp-pod with two containers: frontend and backend. Which command shows logs only from the backend container?

A kubectl logs webapp-pod backend

B kubectl logs webapp-pod --container=frontend

C kubectl get logs webapp-pod -c backend

D kubectl logs webapp-pod -c backend

💡 Hint

Use the -c or --container flag to specify the container name.

The kubectl logs command with -c backend fetches logs from the backend container only. Option D fetches frontend logs, A is invalid syntax, and D uses a wrong command.

🧠 Conceptual

intermediate

Understanding Pod description details

Which section in the output of kubectl describe pod mypod shows the current status of each container inside the Pod?

A Status section

B Containers section

C Conditions section

D Events section

💡 Hint

Look for container names and their state like Running or Waiting.

The Containers section lists each container's current state, restart count, and readiness. Events show recent actions, Conditions show Pod-level health, and Status is a summary.

❓ Troubleshoot

advanced

Diagnosing missing logs from a Pod

You run kubectl logs mypod but get the error: Error from server (BadRequest): container "mypod" in pod "mypod" is not available. What is the most likely cause?

A The Pod has multiple containers and you did not specify which container's logs to show

B The Pod is not running and logs are unavailable

C The Pod name is misspelled

D kubectl logs command requires --all-containers flag

💡 Hint

Think about how logs are fetched when multiple containers exist.

When a Pod has multiple containers, you must specify the container name with -c. Otherwise, kubectl tries to find a container named same as the Pod, which fails.

🔀 Workflow

advanced

Steps to view real-time logs of a Pod

What is the correct sequence of commands to view real-time logs of a Pod named api-server?

A 1,3,4,2

B 1,4,2,3

C 1,4,3,2

D 4,1,2,3

💡 Hint

First confirm Pod exists, then check details, then stream logs.

You first list pods (1), then get details of the specific Pod (3), then stream logs with -f (2). Option 4 is redundant but acceptable after 1 to confirm Pod name.

✅ Best Practice

expert

Efficiently viewing logs from all containers in a Pod

You want to view logs from all containers in a Pod named db-pod simultaneously. Which command achieves this?

A kubectl logs db-pod --all-containers=true

B kubectl logs db-pod -c all

C kubectl logs db-pod --container=all

D kubectl logs db-pod

💡 Hint

Look for a flag that includes logs from every container.

The --all-containers=true flag fetches logs from all containers in the Pod. Options B and C use invalid container names, and D only shows logs from the first container by default.

Practice

1. What command shows detailed information and events about a specific Kubernetes pod?

easy

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

B. kubectl get pods

C. kubectl logs <pod-name>

D. kubectl describe pod <pod-name>

Solution

1. Step 1: Understand the purpose of each command

   kubectl describe pod <pod-name> shows detailed info and events; kubectl get pods lists pods; kubectl logs shows logs; kubectl exec runs commands inside pod.

2. Step 2: Identify the command for detailed pod info

   The command that shows detailed pod information and events is kubectl describe pod <pod-name>.

3. Final Answer:

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

4. Quick Check:

   Detailed pod info = kubectl describe pod [OK]

Hint: Use 'kubectl describe pod' for detailed pod info and events [OK]

Common Mistakes:

• Using 'kubectl get pods' to see detailed info
• Confusing 'kubectl logs' with pod description
• Trying 'kubectl exec' to get pod events

2. Which of the following is the correct syntax to view logs of a pod named myapp-pod?

easy

A. kubectl get logs myapp-pod

B. kubectl logs myapp-pod

C. kubectl describe logs myapp-pod

D. kubectl show logs myapp-pod

Solution

1. Step 1: Recall the correct command for viewing pod logs

   The command to view logs is kubectl logs <pod-name>.

2. Step 2: Match the correct syntax

   Only kubectl logs myapp-pod matches the correct syntax; others are invalid commands.

3. Final Answer:

   kubectl logs myapp-pod -> Option B

4. Quick Check:

   View pod logs = kubectl logs [OK]

Hint: Use 'kubectl logs pod-name' to see pod logs quickly [OK]

Common Mistakes:

• Adding extra words like 'get' or 'describe' with logs
• Using 'kubectl show' which is not a valid command
• Confusing logs command with describe

3. What will be the output of the command kubectl logs mypod --follow?

medium

A. It shows the logs of 'mypod' and continues to stream new log entries live.

B. It shows only the last 10 lines of logs from 'mypod'.

C. It describes the pod 'mypod' with detailed info and events.

D. It executes a shell inside the 'mypod' container.

Solution

1. Step 1: Understand the '--follow' flag with 'kubectl logs'

   The '--follow' option streams logs live, showing new entries as they appear.

2. Step 2: Match the output description

   The command outputs current logs and keeps streaming new logs live for 'mypod'.

3. Final Answer:

   It shows the logs of 'mypod' and continues to stream new log entries live. -> Option A

4. Quick Check:

   kubectl logs --follow = live log streaming [OK]

Hint: Add '--follow' to stream pod logs live as they appear [OK]

Common Mistakes:

• Thinking '--follow' limits logs to last 10 lines
• Confusing logs with pod description
• Assuming it opens a shell inside the pod

4. You run kubectl logs mypod but get an error saying "a container name must be specified for pod mypod". What is the likely cause?

medium

A. The pod 'mypod' has multiple containers and you did not specify which container's logs to show.

B. The pod 'mypod' does not exist in the cluster.

C. You need to use 'kubectl describe pod mypod' instead of logs.

D. The pod 'mypod' is not running yet.

Solution

1. Step 1: Understand the error message

   The error says a container name must be specified, which happens if the pod has multiple containers.

2. Step 2: Identify the cause

   When a pod has more than one container, you must specify which container's logs you want using -c <container-name>.

3. Final Answer:

   The pod 'mypod' has multiple containers and you did not specify which container's logs to show. -> Option A

4. Quick Check:

   Multiple containers need container name for logs [OK]

Hint: Add '-c container-name' if pod has multiple containers [OK]

Common Mistakes:

• Assuming pod doesn't exist without checking
• Using describe instead of logs for viewing logs
• Ignoring container name requirement for multi-container pods

5. You want to monitor logs of a pod named webserver continuously but only for the container named nginx. Which command should you use?

hard

A. kubectl logs webserver --container nginx

B. kubectl describe pod webserver -c nginx --follow

C. kubectl logs webserver -c nginx --follow

D. kubectl logs webserver --tail=0

Solution

1. Step 1: Identify the need to specify container and follow logs

   To monitor logs continuously, use --follow. For multi-container pods, specify container with -c <container-name>.

2. Step 2: Match the correct command syntax

   kubectl logs webserver -c nginx --follow correctly specifies container and streams logs live.

3. Final Answer:

   kubectl logs webserver -c nginx --follow -> Option C

4. Quick Check:

   Use '-c' for container and '--follow' to stream logs [OK]

Hint: Use '-c container --follow' to stream specific container logs live [OK]

Common Mistakes:

• Using 'describe' instead of 'logs' to view logs
• Using '--container' instead of '-c' which is invalid
• Using '--tail=0' which shows no logs