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.

Practice

1. What does scaling a Kubernetes deployment do?

easy

A. Changes the number of running copies (pods) of the app

B. Updates the app's source code automatically

C. Deletes the deployment from the cluster

D. Changes the app's network settings

Solution

1. Step 1: Understand the purpose of scaling

   Scaling means adjusting how many copies of an app run to handle load or save resources.

2. Step 2: Identify what scaling affects

   Scaling changes the number of pods, which are running instances of the app.

3. Final Answer:

   Changes the number of running copies (pods) of the app -> Option A

4. Quick Check:

   Scaling = Change pod count [OK]

Hint: Scaling means changing pod count, not code or network [OK]

Common Mistakes:

• Thinking scaling updates app code
• Confusing scaling with deleting deployments
• Assuming scaling changes network settings

2. Which is the correct command to scale a deployment named webapp to 5 replicas?

easy

A. kubectl scale pods webapp --count=5

B. kubectl update deployment webapp --replicas 5

C. kubectl set replicas webapp 5

D. kubectl scale deployment webapp --replicas=5

Solution

1. Step 1: Recall the correct kubectl scale syntax

   The command to scale is kubectl scale deployment [name] --replicas=[number].

2. Step 2: Match the command to the options

   kubectl scale deployment webapp --replicas=5 matches the correct syntax exactly for deployment webapp to 5 replicas.

3. Final Answer:

   kubectl scale deployment webapp --replicas=5 -> Option D

4. Quick Check:

   Correct scale syntax = kubectl scale deployment webapp --replicas=5 [OK]

Hint: Use 'kubectl scale deployment NAME --replicas=N' exactly [OK]

Common Mistakes:

• Using 'pods' instead of 'deployment'
• Wrong flag like --count instead of --replicas
• Using 'kubectl update' which is invalid for scaling

3. Given this command:
kubectl scale deployment frontend --replicas=3
What will be the number of pods running for the frontend deployment after execution?

medium

A. 0

B. 1

C. 3

D. Depends on cluster resources

Solution

1. Step 1: Understand the scale command effect

   The command sets the number of replicas (pods) to 3 explicitly.

2. Step 2: Determine the pod count after scaling

   After running, Kubernetes will ensure exactly 3 pods for the frontend deployment.

3. Final Answer:

   3 -> Option C

4. Quick Check:

   --replicas=3 means 3 pods [OK]

Hint: Replicas number = pods count after scaling [OK]

Common Mistakes:

• Assuming pods stay at 1 by default
• Thinking scaling depends on cluster resources
• Confusing replicas with CPU or memory

4. You run kubectl scale deployment backend --replicas=two but get an error. What is the problem?

medium

A. The deployment name 'backend' is invalid

B. The replicas value must be a number, not a word

C. The command should use 'kubectl update' instead

D. You need to add --force flag to scale

Solution

1. Step 1: Check the replicas argument type

   The replicas flag requires a numeric value, not a word like 'two'.

2. Step 2: Identify the cause of the error

   Using 'two' causes a syntax error because Kubernetes expects an integer.

3. Final Answer:

   The replicas value must be a number, not a word -> Option B

4. Quick Check:

   Replicas must be numeric [OK]

Hint: Replicas must be a number, not text [OK]

Common Mistakes:

• Using words instead of numbers for replicas
• Thinking deployment name is invalid without checking
• Trying to use 'kubectl update' for scaling

5. You want to scale a deployment named api-server from 2 to 10 replicas but only 6 nodes are available in your cluster. What will happen after running kubectl scale deployment api-server --replicas=10?

hard

A. Only 6 pods will run because of node limits, others stay pending

B. The deployment will scale to 2 pods automatically

C. The command will fail with an error about node count

D. Kubernetes will create 10 pods regardless of node count

Solution

1. Step 1: Understand Kubernetes scheduling with limited nodes

   Kubernetes tries to run all requested pods but can only schedule as many as fit on available nodes.

2. Step 2: Predict pod status with 10 replicas but 6 nodes

   Only 6 pods will be scheduled and running; the other 4 pods remain pending until resources free up.

3. Final Answer:

   Only 6 pods will run because of node limits, others stay pending -> Option A

4. Quick Check:

   Pods limited by nodes = pending pods [OK]

Hint: Pods > nodes means some pods stay pending [OK]

Common Mistakes:

• Assuming all pods run regardless of nodes
• Expecting command to fail on node shortage
• Thinking deployment scales down automatically