Kubernetes - ReplicaSets and Deployments
You want to ensure your Deployment always has exactly 3 running Pods. Which YAML snippet correctly sets this and prevents extra Pods during updates?
You want to ensure your Deployment always has exactly 3 running Pods. Which YAML snippet correctly sets this and prevents extra Pods during updates?
hard📝 Workflow Q8 of 15
Step-by-Step Solution
Solution:
Step 1: Understand maxSurge and maxUnavailable
maxSurge: 0 prevents extra Pods above desired count during updates.Step 2: Check YAML snippet
replicas: 3\nstrategy:\n type: RollingUpdate\n rollingUpdate:\n maxSurge: 0\n maxUnavailable: 1 sets replicas to 3 and maxSurge to 0, maxUnavailable to 1, ensuring no extra Pods.Final Answer:
replicas: 3 with maxSurge: 0 and maxUnavailable: 1 -> Option BQuick Check:
maxSurge=0 prevents extra Pods during rolling update [OK]
Quick Trick: Set maxSurge: 0 to avoid extra Pods during updates [OK]
Common Mistakes:
- Using maxSurge > 0 allows extra Pods
- Choosing Recreate strategy which stops all Pods
- Setting maxUnavailable too high causing downtime
Master "ReplicaSets and Deployments" in Kubernetes
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore Kubernetes Quizzes