Recall & Review
beginner
What is the Recreate update strategy in Kubernetes?
It is a deployment method where all existing pods are stopped before new pods are started. This ensures only one version runs at a time.
Click to reveal answer
intermediate
How does the Recreate strategy differ from RollingUpdate in Kubernetes?
Recreate stops all old pods before starting new ones, causing downtime. RollingUpdate replaces pods gradually, keeping the app available.
Click to reveal answer
beginner
When is it best to use the Recreate update strategy?
Use it when your app cannot run multiple versions at once or when you want a simple update with guaranteed clean start.
Click to reveal answer
beginner
Show the YAML snippet to set Recreate update strategy in a Deployment.
spec:
strategy:
type: Recreate
Click to reveal answer
beginner
What is a possible downside of using the Recreate update strategy?
It causes downtime because the old pods stop before new pods start, so the app is temporarily unavailable.
Click to reveal answer
What happens first in the Recreate update strategy?
✗ Incorrect
In Recreate, Kubernetes stops all old pods before starting new ones.
Which update strategy avoids downtime by updating pods gradually?
✗ Incorrect
RollingUpdate updates pods gradually to keep the app available.
How do you specify the Recreate strategy in a Deployment YAML?
✗ Incorrect
The correct YAML field is 'strategy.type: Recreate'.
What is a main disadvantage of the Recreate update strategy?
✗ Incorrect
Recreate causes downtime because old pods stop before new pods start.
When should you choose Recreate over RollingUpdate?
✗ Incorrect
Recreate is good when the app cannot run multiple versions at once.
Explain how the Recreate update strategy works in Kubernetes and when it is useful.
Think about how pods are replaced and app availability.
You got /3 concepts.
Describe the YAML configuration needed to set the Recreate update strategy in a Deployment.
Look for the 'strategy' field in Deployment YAML.
You got /3 concepts.