Pod lifecycle states in Kubernetes - Mini Project: Build & Apply

Pod lifecycle states

📖 Scenario: You are managing a Kubernetes cluster and want to understand the lifecycle states of a Pod. Pods are the smallest deployable units in Kubernetes that run your containers. Knowing the Pod states helps you monitor and troubleshoot your applications effectively.

🎯 Goal: Learn how to create a Pod manifest, add a label selector, check the Pod's lifecycle state, and display the Pod status using kubectl.

📋 What You'll Learn

Create a Pod manifest YAML file named mypod.yaml with specific metadata and container details

Add a label app: demo to the Pod manifest

Use kubectl get pod with label selector to check the Pod's lifecycle state

Print the Pod's status phase to see its current lifecycle state

💡 Why This Matters

🌍 Real World

Kubernetes Pods run your application containers. Knowing their lifecycle states helps you monitor if your app is running, starting, or has errors.

💼 Career

DevOps engineers and site reliability engineers use Pod lifecycle states daily to ensure applications are healthy and troubleshoot issues quickly.

1

Create the initial Pod manifest

Create a YAML file named mypod.yaml with a Pod manifest that has apiVersion: v1, kind: Pod, metadata name mypod, and a single container named nginx using the image nginx:latest.

Kubernetes

# Create mypod.yaml with apiVersion, kind, metadata name, and container nginx with image nginx:latest
# Your code here

Hint

Remember to include apiVersion, kind, metadata with name, and spec with containers list.

2

Add a label to the Pod manifest

Add a label app: demo under the metadata section in mypod.yaml to help identify the Pod.

Kubernetes

apiVersion: v1
kind: Pod
metadata:
  name: mypod
  # Add label app: demo below
  # Your code here
spec:
  containers:
  - name: nginx
    image: nginx:latest

Hint

Labels go under metadata as a map with key and value.

3

Check Pod lifecycle state using label selector

Use the command kubectl get pod -l app=demo to list the Pod with label app=demo and observe its lifecycle state in the STATUS column.

Kubernetes

# Run kubectl get pod with label selector app=demo
# Your code here

Hint

The -l flag filters Pods by label.

4

Display the Pod's current lifecycle state

Use the command kubectl get pod mypod -o jsonpath='{.status.phase}' to print the current lifecycle state of the Pod named mypod.

Kubernetes

# Run kubectl get pod mypod with jsonpath to print status.phase
# Your code here

Hint

The -o jsonpath= option extracts specific fields from the Pod JSON output.

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