Scaling Deployments in Kubernetes - Step-by-Step Execution

Process Flow - Scaling Deployments

Start: Deployment with 1 replica

↓

Check desired replicas

↓

kubectl scale command issued

↓

Kubernetes updates Deployment spec

↓

ReplicaSet adjusts pods count

↓

New pods created or removed

↓

Deployment reaches desired replicas

↓

End

This flow shows how Kubernetes scales a Deployment by changing the number of pod replicas to match the desired count.

Execution Sample

Kubernetes

kubectl get deployment myapp
kubectl scale deployment myapp --replicas=3
kubectl get pods

This sequence checks current deployment, scales it to 3 replicas, then lists pods to show the change.

Process Table

Step	Command	Action	Deployment Replicas	Pods Running	Result
1	kubectl get deployment myapp	Check current replicas	1	1	Shows 1 replica running
2	kubectl scale deployment myapp --replicas=3	Request scale to 3 replicas	1 -> 3	1	Deployment spec updated, pods not yet changed
3	Kubernetes ReplicaSet	Creates 2 new pods	3	3	Pods count matches desired replicas
4	kubectl get pods	List pods after scaling	3	3	Shows 3 pods running
5	-	No further action	3	3	Scaling complete

💡 Scaling stops when pods running equals desired replicas (3)

Status Tracker

Variable	Start	After Step 2	After Step 3	Final
Deployment Replicas	1	3	3	3
Pods Running	1	1	3	3

Key Moments - 2 Insights

Why does the number of pods not change immediately after the scale command?

After the scale command (Step 2), the Deployment spec updates but Kubernetes needs time to create new pods, which happens in Step 3.

What ensures the pods count matches the desired replicas?

The ReplicaSet controller monitors the Deployment and creates or deletes pods to match the desired replicas, as seen in Step 3.

Visual Quiz - 3 Questions

Look at the execution table, at which step do the pods running first reach 3?

A Step 3

B Step 2

C Step 4

D Step 5

💡 Hint

Check the 'Pods Running' column in the execution table rows

According to the variable tracker, what is the value of Deployment Replicas after Step 2?

A 1

B 2

C 3

D 0

💡 Hint

Look at the 'Deployment Replicas' row under 'After Step 2' in variable_tracker

If the scale command was to 5 replicas instead of 3, how would the pods running change in Step 3?

A Pods running would be 3

B Pods running would be 5

C Pods running would stay at 1

D Pods running would be 0

💡 Hint

Refer to how pods running match desired replicas in the execution_table Step 3

Concept Snapshot

Scaling Deployments in Kubernetes:
- Use 'kubectl scale deployment <name> --replicas=N' to set desired pods
- Deployment updates desired replicas count
- ReplicaSet creates or deletes pods to match desired replicas
- Pods running eventually equals desired replicas
- Check status with 'kubectl get deployment' and 'kubectl get pods'

Full Transcript

Scaling a Kubernetes Deployment means changing how many copies of your app run. You start with a Deployment having 1 pod. When you run 'kubectl scale deployment myapp --replicas=3', Kubernetes updates the Deployment to want 3 pods. The ReplicaSet then creates 2 more pods to reach 3 total. You can see this by listing pods. The process stops when pods running equals the desired replicas. This ensures your app can handle more or less load by adjusting pod count.