Pod lifecycle states in Kubernetes - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a Pod in Kubernetes?

A Pod is the smallest unit in Kubernetes that can run one or more containers together on the same host. It shares storage, network, and specifications for how to run the containers.

beginner

Name the main lifecycle states of a Kubernetes Pod.

The main lifecycle states are: Pending, Running, Succeeded, Failed, and Unknown.

beginner

What does the 'Pending' state mean for a Pod?

Pending means the Pod has been accepted by the Kubernetes system but is waiting to be scheduled onto a node or waiting for container images to be downloaded.

beginner

Explain the 'Running' state of a Pod.

Running means the Pod has been scheduled on a node and all containers inside the Pod have been started successfully and are running.

intermediate

What is the difference between 'Succeeded' and 'Failed' Pod states?

Succeeded means all containers in the Pod have finished successfully and will not restart. Failed means at least one container has terminated with an error or failure.

Which Pod lifecycle state indicates the Pod is waiting to be scheduled or images to download?

A Pending

B Running

C Succeeded

D Failed

Pending means the Pod is accepted but not yet running because it is waiting for scheduling or image download.

What does the 'Running' state of a Pod mean?

A Pod is deleted

B Pod containers are running on a node

C Pod failed to start

D Pod is waiting for scheduling

Running means the Pod is scheduled and all containers are running.

If a Pod has completed all its tasks successfully, what is its state?

A Failed

B Pending

C Succeeded

D Unknown

Succeeded means all containers finished successfully and will not restart.

What does the 'Failed' state indicate for a Pod?

A Pod is deleted

B Pod is running normally

C Pod is waiting for resources

D Pod containers terminated with errors

Failed means one or more containers terminated with errors.

Which Pod state means Kubernetes cannot determine the Pod status?

A Unknown

B Running

C Pending

D Succeeded

Unknown means Kubernetes cannot get the Pod status, often due to node communication issues.

Describe the lifecycle states of a Kubernetes Pod and what each state means.

Think about the Pod's journey from creation to completion or failure.

Explain how Kubernetes handles a Pod that fails to start its containers.

Consider what happens when something goes wrong inside the Pod.

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