Viewing Pod details and logs in Kubernetes - Cheat Sheet & Quick Revision

Recall & Review

beginner

What command shows detailed information about a specific Pod in Kubernetes?

Use kubectl describe pod <pod-name> to see detailed information about a Pod, including its status, events, and container details.

beginner

How do you view the logs of a container inside a Pod?

Use kubectl logs <pod-name> to see the logs of the main container in the Pod. For multiple containers, add -c <container-name>.

beginner

What does the command kubectl get pods show?

It lists all Pods in the current namespace with their names, ready status, restarts, and age.

intermediate

How can you follow logs in real-time for a Pod?

Add the -f option to the logs command: kubectl logs -f <pod-name>. This streams new log entries as they appear.

intermediate

What information can you find in the output of kubectl describe pod?

You see Pod status, container states, events like restarts or failures, and networking details.

Which command shows the logs of a Pod named 'web-app'?

A kubectl describe pod web-app

B kubectl logs web-app

C kubectl get logs web-app

D kubectl show logs web-app

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

How do you get detailed status and events of a Pod?

A kubectl describe pod <pod-name>

B kubectl get pod <pod-name>

C kubectl logs <pod-name>

D kubectl status pod <pod-name>

Use kubectl describe pod <pod-name> to get detailed info including events.

What option allows you to stream logs live?

A -s

B -t

C -f

D -l

The -f option streams logs live as they are generated.

If a Pod has multiple containers, how do you specify which container's logs to view?

A kubectl logs <pod-name> -c <container-name>

B kubectl logs <pod-name> --select <container-name>

C kubectl logs <pod-name> --name <container-name>

D kubectl logs <pod-name> --container <container-name>

Use -c <container-name> to specify the container.

What does kubectl get pods NOT show?

A Pod age

B Pod ready status

C Pod names

D Pod logs

kubectl get pods does not show logs; it shows a summary list of Pods.

Explain how to check the status and recent events of a Kubernetes Pod.

Think about a command that gives you more than just a list.

Describe the steps to view and follow logs of a container inside a Pod.

Logs can be viewed and streamed live.

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