Kubernetes - ReplicaSets and Deployments
You have an app that cannot run multiple versions simultaneously. How do you configure the Deployment update strategy to avoid version conflicts?
You have an app that cannot run multiple versions simultaneously. How do you configure the Deployment update strategy to avoid version conflicts?
hard📝 Workflow Q15 of 15
Step-by-Step Solution
Solution:
Step 1: Identify app requirement
The app cannot run multiple versions at the same time, so pods must not overlap.Step 2: Choose update strategy
Recreate deletes old pods before creating new ones, ensuring no version overlap.Step 3: Rule out other options
RollingUpdate allows overlapping versions, kubectl restart doesn't change strategy, BlueGreen is not a built-in Kubernetes strategy.Final Answer:
Set strategy.type: Recreate to delete old pods before new ones -> Option AQuick Check:
App needs no overlap = use Recreate [OK]
Quick Trick: 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
Master "ReplicaSets and Deployments" in Kubernetes
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore Kubernetes Quizzes