Pod lifecycle states in Kubernetes - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to check if a Pod is in the Running state.

Kubernetes

kubectl get pod my-pod -o jsonpath='{.status.phase}' | grep [1]

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

ARunning

BPending

CSucceeded

DFailed

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'Pending' instead of 'Running' causes wrong status check.

The Pod phase 'Running' means the Pod is active and containers are running.

2fill in blank

medium

Complete the command to list Pods that are in the Pending state.

Kubernetes

kubectl get pods --field-selector status.phase=[1]

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

ARunning

BFailed

CSucceeded

DPending

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'Running' will list active Pods, not pending ones.

The field-selector filters Pods by their phase. 'Pending' shows Pods waiting to start.

3fill in blank

hard

Fix the error in the command to get the Pod phase correctly.

Kubernetes

kubectl get pod my-pod -o jsonpath='{.status.[1]'

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

Aphase

Bcondition

Cstatus

Dstate

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'state' or 'condition' causes no output or errors.

The correct JSON path key for Pod lifecycle state is 'phase'.

4fill in blank

hard

Fill both blanks to create a command that lists Pods in Running or Succeeded states.

Kubernetes

kubectl get pods --field-selector='status.phase in ([1],[2])'

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

ARunning

BPending

CSucceeded

DFailed

Attempts:

3 left

💡 Hint

Common Mistakes

Using Pending or Failed will not show desired Pod states.

This command filters Pods that are either Running or have Succeeded.

5fill in blank

hard

Fill all three blanks to create a command that watches Pods entering Running state with a label.

Kubernetes

kubectl get pods -l app=[1] --field-selector status.phase=[2] --watch=[3]

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

Afrontend

BRunning

Ctrue

Dfalse

Attempts:

3 left

💡 Hint

Common Mistakes

Using false for --watch disables live updates.

This command watches Pods labeled 'frontend' as they enter the Running phase.

Practice

1. Which of the following is a valid lifecycle state of a Kubernetes Pod?

easy

A. Uploading

B. Compiling

C. Downloading

D. Running

Solution

1. Step 1: Recall Pod lifecycle states

   Kubernetes Pods have specific states like Pending, Running, Succeeded, Failed, and Unknown.

2. Step 2: Match options with valid states

   Among the options, only "Running" is a valid Pod state.

3. Final Answer:

   Running -> Option D

4. Quick Check:

   Pod state "Running" = C [OK]

Hint: Remember common Pod states: Pending, Running, Succeeded, Failed [OK]

Common Mistakes:

• Confusing Pod states with unrelated terms
• Thinking 'Compiling' or 'Uploading' are Pod states

2. Which kubectl command shows the current state of all Pods in the default namespace?

easy

A. kubectl get pods

B. kubectl create pods

C. kubectl logs pods

D. kubectl describe pods

Solution

1. Step 1: Understand commands for Pod status

   kubectl get pods lists Pods with their current states briefly.

2. Step 2: Differentiate from other commands

   kubectl describe pods shows detailed info, kubectl logs shows logs, and kubectl create creates resources.

3. Final Answer:

   kubectl get pods -> Option A

4. Quick Check:

   Command to list Pod states = D [OK]

Hint: Use 'kubectl get pods' to quickly see Pod states [OK]

Common Mistakes:

• Using 'kubectl describe pods' for a quick state overview
• Confusing 'kubectl logs' with status commands

3. Given the output of kubectl get pods below, what is the current state of the Pod named web-server?

NAME         READY   STATUS    RESTARTS   AGE
web-server   1/1     Running   0          5m

medium

A. Pending

B. Succeeded

C. Running

D. Failed

Solution

1. Step 1: Read the STATUS column for the Pod

   The STATUS column shows "Running" for the Pod named web-server.

2. Step 2: Confirm the Pod is active

   READY is 1/1, meaning all containers are ready, confirming the Pod is running.

3. Final Answer:

   Running -> Option C

4. Quick Check:

   Pod status shown as Running = B [OK]

Hint: Check STATUS column in 'kubectl get pods' output [OK]

Common Mistakes:

• Confusing READY count with STATUS
• Assuming 1/1 means Pending instead of Running

4. You see a Pod stuck in the Pending state for a long time. Which of the following is the most likely cause?

medium

A. No available nodes meet Pod resource requests

B. Pod containers crashed repeatedly

C. Pod completed its task successfully

D. Pod is actively running containers

Solution

1. Step 1: Understand what Pending means

   Pending means the Pod is accepted but not yet scheduled to a node.

2. Step 2: Identify common reasons for Pending

   One common reason is no nodes have enough resources to run the Pod.

3. Final Answer:

   No available nodes meet Pod resource requests -> Option A

4. Quick Check:

   Pending due to resource shortage = A [OK]

Hint: Pending often means no suitable node available [OK]

Common Mistakes:

• Confusing Pending with container crash issues
• Thinking Pending means Pod finished successfully

5. A Pod shows the status CrashLoopBackOff. What is the best first step to diagnose the problem?

hard

A. Delete the Pod immediately to stop the crash

B. Run kubectl logs <pod-name> to check container logs

C. Scale the deployment to zero replicas

D. Restart the Kubernetes cluster

Solution

1. Step 1: Understand CrashLoopBackOff meaning

   This status means the container is repeatedly crashing and restarting.

2. Step 2: Use logs to find the cause

   Checking container logs with kubectl logs helps identify the error causing crashes.

3. Final Answer:

   Run kubectl logs <pod-name> to check container logs -> Option B

4. Quick Check:

   Check logs first for CrashLoopBackOff = A [OK]

Hint: Use logs to diagnose CrashLoopBackOff issues first [OK]

Common Mistakes:

• Deleting Pod without diagnosing
• Restarting cluster unnecessarily
• Scaling deployment without root cause