Viewing Pod details and logs in Kubernetes - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the command to view details of a pod named 'webapp'.

Kubernetes

kubectl [1] webapp

Drag options to blanks, or click blank then click option'

Alogs

Bget

Cdescribe

Ddelete

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'kubectl get' only lists pods without detailed info.

Using 'kubectl logs' shows logs, not pod details.

The kubectl describe command shows detailed information about a pod, including events and status.

2fill in blank

medium

Complete the command to view logs of a pod named 'backend'.

Kubernetes

kubectl [1] backend

Drag options to blanks, or click blank then click option'

Adescribe

Bget

Cexec

Dlogs

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'kubectl describe' shows details but not logs.

Using 'kubectl exec' runs commands inside the pod, not logs.

The kubectl logs command shows the logs of a pod, useful for debugging.

3fill in blank

hard

Fix the error in the command to follow logs of a pod named 'api-server'.

Kubernetes

kubectl logs api-server [1]

Drag options to blanks, or click blank then click option'

A-f

B--tail

C-n

D--all

Attempts:

3 left

💡 Hint

Common Mistakes

Using '--tail' only shows last lines but does not follow.

Using '-n' is for namespace, not for following logs.

The -f flag makes kubectl logs follow the log output live.

4fill in blank

hard

Fill both blanks to get logs from the second container in a pod named 'multi-container-pod'.

Kubernetes

kubectl logs multi-container-pod [1] [2]

Drag options to blanks, or click blank then click option'

A-c

Bcontainer-2

C--container

Dcontainer-1

Attempts:

3 left

💡 Hint

Common Mistakes

Not specifying container when pod has multiple containers causes error.

Using wrong container name or flag.

Use -c or --container to specify which container's logs to view. Here, container-2 is the second container.

5fill in blank

hard

Fill all three blanks to get the last 100 lines of logs from container 'web' in pod 'frontend' in namespace 'prod'.

Kubernetes

kubectl logs [1] [2] [3] --tail=100

Drag options to blanks, or click blank then click option'

A-n prod

B-c web

Cfrontend

D--namespace=dev

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing up namespace or container flags.

Forgetting to specify container when pod has multiple containers.

The command specifies the pod name frontend, container web with -c, and namespace prod with -n. The --tail=100 shows last 100 lines.

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