Why Pods are the smallest deployable unit in Kubernetes - Visual Breakdown

Process Flow - Why Pods are the smallest deployable unit

User defines containers

↓

Containers grouped into Pod

↓

Pod created as single unit

↓

Pod scheduled on Node

↓

Pod runs containers together

↓

Pod managed as one deployable unit

Containers are grouped into a Pod, which is created, scheduled, and managed as a single unit in Kubernetes.

Execution Sample

Kubernetes

apiVersion: v1
kind: Pod
metadata:
  name: my-pod
spec:
  containers:
  - name: app-container
    image: nginx

This YAML defines a Pod with one container running the nginx image.

Process Table

Step	Action	Result	System State
1	User writes Pod YAML with containers	Pod spec ready	Pod spec includes 1 container
2	kubectl apply Pod YAML	Pod object created	Pod object stored in Kubernetes API
3	Scheduler assigns Pod to Node	Pod scheduled	Pod assigned to specific Node
4	Kubelet on Node starts containers	Containers running	Containers inside Pod running on Node
5	Pod runs as single unit	Pod active	Pod and containers managed together
6	User updates Pod spec	Pod updated	Pod replaced or restarted as one unit
7	Pod deleted	All containers stopped	Pod and containers removed together

💡 Pod lifecycle ends when Pod is deleted, stopping all containers together

Status Tracker

Variable	Start	After Step 2	After Step 3	After Step 4	After Step 7
Pod Object	None	Created	Scheduled	Running	Deleted
Containers	None	Defined in Pod	Pending start	Running	Stopped

Key Moments - 3 Insights

Why can't we deploy containers individually without a Pod?

Containers need a Pod because Kubernetes manages Pods as the smallest deployable unit, grouping containers that share resources and lifecycle. See execution_table steps 1-5.

What happens to containers when the Pod is deleted?

All containers inside the Pod stop together because the Pod is the unit Kubernetes manages. See execution_table step 7.

Why does Kubernetes schedule Pods, not individual containers?

Scheduling Pods ensures containers that belong together run on the same Node with shared resources. See execution_table step 3.

Visual Quiz - 3 Questions

Look at the execution table, at which step are containers actually started on the Node?

A Step 2

B Step 3

C Step 4

D Step 5

💡 Hint

Check the 'Action' and 'Result' columns for when containers begin running.

According to the variable tracker, what is the state of the Pod Object after Step 3?

A Created

B Scheduled

C Running

D Deleted

💡 Hint

Look at the 'Pod Object' row and the 'After Step 3' column.

If the Pod is deleted at Step 7, what happens to the containers?

A They stop together with the Pod

B They restart automatically

C They keep running independently

D They move to another Node

💡 Hint

Refer to execution_table step 7 and variable_tracker containers state.

Concept Snapshot

Pods group one or more containers into a single deployable unit.
Kubernetes schedules and manages Pods, not individual containers.
Containers in a Pod share resources and lifecycle.
Deleting a Pod stops all its containers together.
Pods ensure containers run on the same Node with shared context.

Full Transcript

In Kubernetes, containers are grouped into Pods, which are the smallest deployable units. A Pod is defined by a YAML spec listing its containers. When you apply this spec, Kubernetes creates a Pod object. The scheduler assigns the Pod to a Node, and the Node's kubelet starts the containers inside the Pod. All containers in a Pod share resources and lifecycle, so they start, run, and stop together. When you delete a Pod, all its containers stop at once. This grouping allows Kubernetes to manage related containers as one unit, ensuring they run on the same Node and share network and storage. This is why Pods are the smallest deployable unit in Kubernetes.

Practice

1. Why are Pods considered the smallest deployable unit in Kubernetes?

easy

A. Because they group one or more containers that share resources like network and storage

B. Because they represent a single container only

C. Because they are the smallest unit of storage in Kubernetes

D. Because they are the smallest unit of CPU allocation

Solution

1. Step 1: Understand what a Pod contains

   A Pod groups one or more containers that share the same network and storage resources.

2. Step 2: Identify why this grouping matters

   This grouping allows containers to be managed and deployed together as a single unit.

3. Final Answer:

   Because they group one or more containers that share resources like network and storage -> Option A

4. Quick Check:

   Pod = smallest deployable unit grouping containers [OK]

Hint: Pods group containers sharing resources, making them smallest units [OK]

Common Mistakes:

• Thinking Pods are single containers only
• Confusing Pods with storage units
• Assuming Pods allocate CPU individually

2. Which of the following is the correct way to define a Pod in a Kubernetes YAML file?

easy

A. apiVersion: v1\nkind: Service\nmetadata:\n name: mypod\nspec:\n containers:\n - name: mycontainer\n image: nginx

B. apiVersion: v1\nkind: Pod\nmetadata:\n name: mypod\nspec:\n containers:\n - name: mycontainer\n image: nginx

C. apiVersion: apps/v1\nkind: Pod\nmetadata:\n name: mypod\nspec:\n containers:\n - name: mycontainer\n image: nginx

D. apiVersion: v1\nkind: Pod\nmetadata:\n name: mypod\nspec:\n image: nginx

Solution

1. Step 1: Check the apiVersion and kind fields

   The correct apiVersion for a Pod is 'v1' and kind is 'Pod'.

2. Step 2: Verify the containers section

   The containers must be listed under spec with name and image fields inside a list.

3. Final Answer:

   apiVersion: v1\nkind: Pod\nmetadata:\n name: mypod\nspec:\n containers:\n - name: mycontainer\n image: nginx -> Option B

4. Quick Check:

   Pod YAML needs apiVersion v1 and kind Pod [OK]

Hint: Pod YAML uses apiVersion v1 and kind Pod with containers list [OK]

Common Mistakes:

• Using wrong kind like Service instead of Pod
• Missing containers list under spec
• Wrong apiVersion for Pod

3. Given this Pod spec snippet, what will happen when it is deployed?

apiVersion: v1
kind: Pod
metadata:
  name: testpod
spec:
  containers:
  - name: app
    image: busybox
    command: ['sleep', '3600']
  - name: sidecar
    image: busybox
    command: ['sleep', '3600']

medium

A. Containers will run but on separate Pods automatically

B. Only the first container will run, the second will be ignored

C. The Pod will fail because multiple containers are not allowed

D. Two containers will run together sharing the same network and storage

Solution

1. Step 1: Analyze the Pod spec with multiple containers

   The spec defines two containers inside one Pod, which is allowed and common.

2. Step 2: Understand container behavior in a Pod

   Both containers run together sharing the Pod's network and storage resources.

3. Final Answer:

   Two containers will run together sharing the same network and storage -> Option D

4. Quick Check:

   Multiple containers in one Pod run together sharing resources [OK]

Hint: Multiple containers in one Pod run together sharing network/storage [OK]

Common Mistakes:

• Thinking only one container runs per Pod
• Assuming multiple containers cause Pod failure
• Believing containers run in separate Pods automatically

4. You deployed a Pod with two containers, but only one container is running. What is the most likely cause?

medium

A. The Pod spec must list containers under metadata, not spec

B. Pods can only run one container at a time

C. The second container's image name is incorrect causing it to fail

D. Kubernetes does not support multiple containers in a Pod

Solution

1. Step 1: Recall Pod container rules

   Pods can run multiple containers simultaneously if defined correctly.

2. Step 2: Identify common failure reasons

   If one container is not running, a common cause is an incorrect image name or failure to pull the image.

3. Final Answer:

   The second container's image name is incorrect causing it to fail -> Option C

4. Quick Check:

   Container failure often due to wrong image name [OK]

Hint: Check container image names if some containers don't run [OK]

Common Mistakes:

• Believing Pods run only one container
• Misplacing containers under metadata
• Thinking Kubernetes disallows multiple containers in Pods

5. You want to deploy two tightly coupled containers that must share the same IP address and storage. Why should you deploy them in a single Pod instead of separate Pods?

hard

A. Because containers in the same Pod share network and storage, enabling tight coupling

B. Because separate Pods cannot run containers at the same time

C. Because Kubernetes does not allow multiple Pods to communicate

D. Because Pods automatically merge containers into one process

Solution

1. Step 1: Understand resource sharing in Pods

   Containers in the same Pod share the same IP address and storage volumes.

2. Step 2: Compare with separate Pods

   Separate Pods have different IPs and isolated storage, making tight coupling harder.

3. Step 3: Reason why single Pod is best

   Deploying tightly coupled containers in one Pod ensures they can communicate easily and share data.

4. Final Answer:

   Because containers in the same Pod share network and storage, enabling tight coupling -> Option A

5. Quick Check:

   Shared network/storage in Pod enables tight container coupling [OK]

Hint: Use one Pod to share IP and storage for tightly coupled containers [OK]

Common Mistakes:

• Thinking separate Pods can't run simultaneously
• Believing Kubernetes blocks Pod communication
• Assuming Pods merge containers into one process