Rolling update strategy in Kubernetes - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a rolling update strategy in Kubernetes?

A rolling update strategy gradually replaces old versions of an application with new ones without downtime by updating pods one at a time.

beginner

How does Kubernetes ensure zero downtime during a rolling update?

Kubernetes updates pods incrementally, keeping some old pods running until new pods are ready, so the service stays available.

intermediate

What is the role of 'maxUnavailable' in a rolling update?

'maxUnavailable' sets the maximum number of pods that can be unavailable during the update, controlling update speed and availability.

intermediate

What does 'maxSurge' control in a rolling update?

'maxSurge' controls how many extra pods can be created above the desired number during the update to speed up deployment.

beginner

Why is a rolling update preferred over recreating all pods at once?

Because it avoids downtime by updating pods gradually, keeping the application available during the process.

What does a rolling update do in Kubernetes?

A Updates pods one by one without downtime

B Deletes all pods and creates new ones at once

C Stops the service during update

D Updates only half of the pods

A rolling update updates pods incrementally to avoid downtime.

Which setting controls how many pods can be unavailable during a rolling update?

A maxUnavailable

B maxSurge

C replicas

D minReadySeconds

'maxUnavailable' sets the max number of pods that can be down during update.

What does 'maxSurge' allow during a rolling update?

A Pods to restart automatically

B Pods to be deleted faster

C Extra pods above desired count

D Pods to be scaled down

'maxSurge' allows creating extra pods temporarily to speed up updates.

Why is rolling update strategy important?

A It updates only one pod forever

B It prevents downtime during updates

C It stops the service temporarily

D It deletes all pods quickly

Rolling updates keep the service running by updating pods gradually.

During a rolling update, what happens to old pods?

A They are paused

B They are deleted immediately

C They keep running forever

D They are terminated only after new pods are ready

Old pods stay running until new pods are ready to avoid downtime.

Explain how a rolling update works in Kubernetes and why it is useful.

Think about how pods are updated one by one and how availability is maintained.

Describe the difference between maxUnavailable and maxSurge in a rolling update.

One controls how many pods can be offline, the other controls extra pods created.