Recreate update strategy in Kubernetes - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

What happens during a Recreate update strategy in Kubernetes?

In Kubernetes, when you use the Recreate update strategy for a Deployment, what is the behavior during an update?

A Kubernetes deletes all existing pods before creating new ones.

B Kubernetes creates new pods first, then deletes old pods after they are ready.

C Kubernetes updates pods one by one without downtime.

D Kubernetes scales up new pods and keeps old pods running indefinitely.

💡 Hint

Think about whether old pods and new pods run at the same time or not.

The Recreate strategy deletes all existing pods before starting new pods, causing downtime but ensuring no two versions run simultaneously.

💻 Command Output

intermediate

Output of Deployment with Recreate strategy during update

Given this Deployment YAML snippet using Recreate strategy, what will be the status of pods during an update?

Kubernetes

strategy:
  type: Recreate

A Old pods and new pods run simultaneously during update.

B Pods are updated one at a time with zero downtime.

C Old pods are terminated before new pods start; no pods run simultaneously.

D New pods start first, then old pods terminate after readiness.

💡 Hint

Recreate means 'remove then create'.

With Recreate, Kubernetes deletes old pods before creating new ones, so no overlap occurs.

❓ Configuration

advanced

Correct YAML for Recreate update strategy

Which YAML snippet correctly configures a Deployment to use the Recreate update strategy?

A

strategy:
  rollingUpdate:
    maxUnavailable: 1

B

strategy:
  type: RollingUpdate

C

updateStrategy:
  type: Recreate

D

strategy:
  type: Recreate

💡 Hint

Look for the correct field name and value for Recreate.

The correct field is strategy.type with value Recreate. Other options are either wrong field names or different strategies.

❓ Troubleshoot

advanced

Why does a Deployment with Recreate strategy cause downtime?

You notice your application becomes unavailable during Deployment updates using the Recreate strategy. Why does this happen?

A Because all old pods are deleted before new pods start, causing downtime.

B Because new pods fail to start due to resource limits.

C Because pods are updated one by one, causing slow rollout.

D Because the Deployment uses RollingUpdate strategy instead.

💡 Hint

Think about pod availability during the update process.

Recreate deletes all old pods before creating new ones, so there is a period with no pods running, causing downtime.

✅ Best Practice

expert

When to prefer Recreate update strategy over RollingUpdate?

In which scenario is using the Recreate update strategy recommended instead of RollingUpdate?

A When zero downtime is critical for the application.

B When the application cannot handle multiple versions running simultaneously.

C When you want to update pods gradually without downtime.

D When you want to scale pods automatically based on load.

💡 Hint

Consider application compatibility with multiple versions running at once.

Recreate is best when running multiple versions simultaneously causes issues, such as with certain databases or stateful apps.

Practice

1. What does the Recreate update strategy do in Kubernetes?

easy

A. Deletes old pods before creating new ones, causing downtime

B. Creates new pods first, then deletes old pods to avoid downtime

C. Updates pods one by one without deleting any

D. Scales pods up and down simultaneously during update

Solution

1. Step 1: Understand the Recreate strategy behavior

   The Recreate strategy deletes all old pods before starting new pods, which causes downtime.

2. Step 2: Compare with other strategies

   Other strategies like RollingUpdate create new pods before deleting old ones to avoid downtime, unlike Recreate.

3. Final Answer:

   Deletes old pods before creating new ones, causing downtime -> Option A

4. Quick Check:

   Recreate = delete old pods first [OK]

Hint: Recreate means delete old pods first, then create new [OK]

Common Mistakes:

• Confusing Recreate with RollingUpdate
• Thinking Recreate avoids downtime
• Assuming pods update one by one

2. Which YAML snippet correctly sets the update strategy to Recreate in a Deployment?

easy

A. strategy:\n type: RollingUpdate

B. strategy:\n type: Recreate

C. updateStrategy:\n type: Recreate

D. deploymentStrategy:\n type: Recreate

Solution

1. Step 1: Identify correct field name for update strategy

   The correct field under Deployment spec is strategy with a nested type.

2. Step 2: Check correct value for Recreate

   The value must be exactly Recreate to set that strategy.

3. Final Answer:

   strategy:\n type: Recreate -> Option B

4. Quick Check:

   strategy.type = Recreate [OK]

Hint: Use 'strategy.type: Recreate' exactly in Deployment spec [OK]

Common Mistakes:

• Using wrong field names like updateStrategy or deploymentStrategy
• Setting type to RollingUpdate instead of Recreate
• Incorrect indentation or YAML syntax

3. Given this Deployment with strategy.type: Recreate, what happens when you update the container image?

medium

A. Pods update one by one without downtime

B. New pods start first, then old pods terminate, no downtime

C. All old pods are terminated before new pods start, causing downtime

D. Pods scale up and down simultaneously

Solution

1. Step 1: Understand Recreate update behavior on image change

   When the image changes, Recreate deletes all old pods before creating new pods.

2. Step 2: Recognize downtime impact

   Because old pods are deleted first, there is downtime until new pods are ready.

3. Final Answer:

   All old pods are terminated before new pods start, causing downtime -> Option C

4. Quick Check:

   Recreate update = downtime during pod replacement [OK]

Hint: Recreate deletes old pods first, causing downtime on update [OK]

Common Mistakes:

• Assuming pods update without downtime
• Confusing with RollingUpdate behavior
• Thinking pods update one by one

4. You set strategy.type: Recreate but notice pods are not deleted before new ones start. What is the likely issue?

medium

A. The Deployment has maxUnavailable set to 0, causing RollingUpdate behavior

B. The Deployment is using StatefulSet instead of Deployment

C. The pods have readinessProbe misconfigured

D. The strategy type is misspelled or incorrectly set

Solution

1. Step 1: Check strategy type correctness

   If pods are not deleted first, the strategy type may be misspelled or set incorrectly, so Kubernetes defaults to RollingUpdate.

2. Step 2: Rule out other causes

   maxUnavailable affects RollingUpdate, readinessProbe affects pod readiness, and StatefulSet is a different resource type.

3. Final Answer:

   The strategy type is misspelled or incorrectly set -> Option D

4. Quick Check:

   Misspelled strategy.type causes default RollingUpdate [OK]

Hint: Check exact spelling of strategy.type: Recreate [OK]

Common Mistakes:

• Assuming maxUnavailable affects Recreate
• Ignoring YAML syntax errors
• Confusing Deployment with StatefulSet

5. You have an app that cannot run multiple versions simultaneously. How do you configure the Deployment update strategy to avoid version conflicts?

hard

A. Set strategy.type: Recreate to delete old pods before new ones

B. Set strategy.type: RollingUpdate with maxSurge=1

C. Use kubectl rollout restart without changing strategy

D. Set strategy.type: BlueGreen for zero downtime

Solution

1. Step 1: Identify app requirement

   The app cannot run multiple versions at the same time, so pods must not overlap.

2. Step 2: Choose update strategy

   Recreate deletes old pods before creating new ones, ensuring no version overlap.

3. Step 3: Rule out other options

   RollingUpdate allows overlapping versions, kubectl restart doesn't change strategy, BlueGreen is not a built-in Kubernetes strategy.

4. Final Answer:

   Set strategy.type: Recreate to delete old pods before new ones -> Option A

5. Quick Check:

   App needs no overlap = use Recreate [OK]

Hint: Use Recreate strategy to avoid running multiple versions [OK]

Common Mistakes:

• Choosing RollingUpdate which allows overlap
• Thinking kubectl restart changes update strategy
• Assuming BlueGreen is a native Kubernetes strategy