Microservices - Orchestration with Kubernetes
To update a microservice with zero downtime, which Kubernetes Deployment update strategy should be configured?
To update a microservice with zero downtime, which Kubernetes Deployment update strategy should be configured?
hard📝 Trade-off Q8 of 15
Step-by-Step Solution
Solution:
Step 1: Understand update strategies
RollingUpdate allows gradual replacement of Pods, maintaining availability during updates.Step 2: Configure maxUnavailable
Setting maxUnavailable to 0 ensures no Pods are taken down before replacements are ready, enabling zero downtime.Step 3: Evaluate other options
Recreate causes downtime; Blue/Green and OnDelete require manual intervention and are not native Deployment strategies.Final Answer:
RollingUpdate strategy with maxUnavailable set to 0 -> Option BQuick Check:
RollingUpdate with zero maxUnavailable ensures zero downtime [OK]
Quick Trick: Use RollingUpdate with maxUnavailable=0 for zero downtime [OK]
Common Mistakes:
MISTAKES- Choosing Recreate which causes downtime
- Confusing manual Blue/Green with Deployment strategies
- Ignoring maxUnavailable setting
Master "Orchestration with Kubernetes" in Microservices
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore Microservices Quizzes