Pod lifecycle states in Kubernetes - Commands & Configuration

Introduction

Pods are the smallest units in Kubernetes that run containers. Understanding their lifecycle states helps you know what is happening to your app at each step, like when it starts, runs, or stops.

When you want to check if your app is running correctly inside Kubernetes.

When your pod is stuck and you need to know why it is not starting.

When you want to monitor the health and status of your app containers.

When you need to debug issues related to pod crashes or restarts.

When you want to understand how Kubernetes manages your app's containers over time.

Commands

This command creates a pod named example-pod running the nginx container. The restart=Never flag means Kubernetes will not restart the pod automatically if it stops.

Terminal

kubectl run example-pod --image=nginx --restart=Never

Expected Output

pod/example-pod created

→

--image - Specifies the container image to run inside the pod

→

--restart - Controls the pod restart policy; Never means no automatic restart

This command shows the current state of the example-pod, such as Pending, Running, or Completed.

Terminal

kubectl get pods example-pod

Expected Output

NAME          READY   STATUS    RESTARTS   AGE

example-pod   1/1     Running   0          10s

This command gives detailed information about the pod, including events and state changes, helping you understand its lifecycle transitions.

Terminal

kubectl describe pod example-pod

Expected Output

Name:         example-pod

Namespace:    default

Status:       Running

Containers:

  nginx:

    Container ID:   docker://abcdef123456

    Image:          nginx

    State:          Running

      Started:      Thu, 01 Jan 1970 00:00:10 +0000

Events:

  Type    Reason     Age   From               Message

  ----    ------     ----  ----               -------

  Normal  Scheduled  1m    default-scheduler  Successfully assigned default/example-pod to node-1

  Normal  Pulled     1m    kubelet            Container image "nginx" already present on machine

  Normal  Created    1m    kubelet            Created container nginx

  Normal  Started    1m    kubelet            Started container nginx

This command deletes the example-pod, which moves it to the Terminating state before removal.

Terminal

kubectl delete pod example-pod

Expected Output

pod "example-pod" deleted

Key Concept

If you remember nothing else from pod lifecycle states, remember: pods move through states like Pending, Running, and Terminating to show their current condition.

Common Mistakes

Trying to create a pod without specifying a container image

Kubernetes needs a container image to run inside the pod; without it, the pod cannot start.

Always specify a valid container image using the --image flag when creating a pod.

Assuming a pod is running just because it exists

A pod can exist but be in Pending or Failed state, meaning it is not ready to serve your app.

Use kubectl get pods and check the STATUS column to confirm the pod is Running.

Deleting a pod without understanding it will be Terminating first

The pod does not disappear instantly; it goes through Terminating state which may take time if cleanup is needed.

Wait for the pod to fully terminate before assuming it is gone.

Summary

Create a pod with kubectl run specifying the container image and restart policy.

Check the pod's current lifecycle state with kubectl get pods.

Use kubectl describe pod to see detailed state changes and events.

Delete the pod to move it to the Terminating state before removal.

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