Viewing Pod details and logs in Kubernetes - Step-by-Step Execution

Process Flow - Viewing Pod details and logs

Start: Identify Pod

↓

kubectl get pods

↓

Select Pod Name

↓

kubectl describe pod

↓

View Pod Details

↓

End: Analyze Output

First, list pods to find the pod name. Then use 'kubectl describe pod' to see details or 'kubectl logs pod' to see logs.

Execution Sample

Kubernetes

kubectl get pods
kubectl describe pod my-pod
kubectl logs my-pod

List pods, then show details and logs of a specific pod named 'my-pod'.

Process Table

Step	Command	Action	Output Summary
1	kubectl get pods	List all pods in current namespace	Displays pod names, statuses, and age
2	kubectl describe pod my-pod	Show detailed info about 'my-pod'	Shows pod metadata, status, containers, events
3	kubectl logs my-pod	Show logs from 'my-pod' containers	Outputs container logs line by line
4	-	End of commands	No further output

💡 All commands executed; pod details and logs displayed for analysis.

Status Tracker

Variable	Start	After Step 1	After Step 2	After Step 3
pod_list	empty	['my-pod', 'other-pod']	unchanged	unchanged
selected_pod	none	none	'my-pod'	'my-pod'
pod_details	none	none	metadata + status + events	unchanged
pod_logs	none	none	none	log lines from container

Key Moments - 2 Insights

Why do we run 'kubectl get pods' before describing or viewing logs?

Because 'kubectl get pods' shows the pod names available, so you know which pod to describe or get logs from, as seen in execution_table step 1.

What is the difference between 'kubectl describe pod' and 'kubectl logs'?

'kubectl describe pod' shows detailed pod info like status and events, while 'kubectl logs' shows the actual output from the pod's containers, as shown in steps 2 and 3.

Visual Quiz - 3 Questions

Look at the execution table, what command lists all pods?

A kubectl get pods

B kubectl describe pod my-pod

C kubectl logs my-pod

D kubectl delete pod my-pod

💡 Hint

Check Step 1 in the execution_table for the command that lists pods.

At which step do we see the pod's events and status details?

A Step 1

B Step 2

C Step 3

D Step 4

💡 Hint

Refer to Step 2 in execution_table where 'kubectl describe pod' is run.

If you want to see what your pod is printing out, which command would you use?

A kubectl get pods

B kubectl describe pod my-pod

C kubectl logs my-pod

D kubectl exec my-pod

💡 Hint

Look at Step 3 in execution_table for the command that shows pod logs.

Concept Snapshot

kubectl get pods  # List pods in namespace
kubectl describe pod <pod-name>  # Show detailed pod info
kubectl logs <pod-name>  # Show container logs
Use get pods first to find pod names
Describe shows status and events
Logs show what the pod outputs

Full Transcript

To view pod details and logs, first run 'kubectl get pods' to list all pods and find the pod name. Then use 'kubectl describe pod <pod-name>' to see detailed information like status, containers, and events. To see what the pod is printing, run 'kubectl logs <pod-name>'. This sequence helps you understand pod state and troubleshoot by checking logs.

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