Which statement best describes Pod Disruption Budgets?

Which statement best describes Pod Disruption Budgets?

• A. They ensure Pods are always scheduled on the same Node
• B. They control the automatic scaling of Pods
• C. They guarantee zero disruptions during updates
• D. They maintain a minimum number of available replicas during voluntary disruptions

Answer: (D)

Pod Disruption Budgets set a guardrail for voluntary disruptions by specifying how many pods in a group can be evicted at once without violating availability. They are used during maintenance actions like node drains or rolling updates to ensure a minimum number of pods remains available. This is why the statement describing maintaining a minimum number of available replicas during voluntary disruptions is the best fit: the budget guarantees that at least a certain amount of pods stay up while disruptions are ongoing. It’s important to note that PDBs can still allow some disruption, but only up to the defined threshold; they do not promise zero disruptions. They also don’t control scheduling on specific nodes or automatic scaling—those are handled by other features.

Pod Disruption Budgets set a guardrail for voluntary disruptions by specifying how many pods in a group can be evicted at once without violating availability. They are used during maintenance actions like node drains or rolling updates to ensure a minimum number of pods remains available. This is why the statement describing maintaining a minimum number of available replicas during voluntary disruptions is the best fit: the budget guarantees that at least a certain amount of pods stay up while disruptions are ongoing. It’s important to note that PDBs can still allow some disruption, but only up to the defined threshold; they do not promise zero disruptions. They also don’t control scheduling on specific nodes or automatic scaling—those are handled by other features.