Bird
0
0

Why might a Pod Disruption Budget with minAvailable: 0 be useful in a production environment?

hard📝 Conceptual Q10 of 15
Kubernetes - Production Best Practices
Why might a Pod Disruption Budget with minAvailable: 0 be useful in a production environment?
AIt prevents any pod disruptions, ensuring full availability
BIt allows all pods to be disrupted voluntarily, useful for maintenance
CIt causes Kubernetes to ignore the PDB entirely
DIt sets a default minimum of 1 pod available
Step-by-Step Solution
Solution:
  1. Step 1: Interpret minAvailable: 0 meaning

    minAvailable: 0 means no pods are required to be up during voluntary disruptions.
  2. Step 2: Understand use case

    This allows all pods to be disrupted voluntarily, which can be useful during maintenance or rolling upgrades.
  3. Final Answer:

    Allows all pods to be disrupted voluntarily, useful for maintenance -> Option B
  4. Quick Check:

    minAvailable 0 allows all pods disruption = B [OK]
Quick Trick: minAvailable 0 allows full voluntary pod disruption [OK]
Common Mistakes:
  • Thinking minAvailable 0 prevents disruptions
  • Assuming PDB is ignored with minAvailable 0
  • Confusing minAvailable 0 with minAvailable 1

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Kubernetes Quizzes