Pod Disruption Budgets are used to ensure what during voluntary disruptions?

Pod Disruption Budgets are used to ensure what during voluntary disruptions?

• A. It enforces a maximum pod count.
• B. It ensures a minimum number of pods remain running during voluntary disruptions.
• C. It governs network policies.
• D. It sets resource quotas.

Answer: (D)

Pod Disruption Budgets focus on keeping services available during voluntary disruptions by guaranteeing a minimum number of pods stay running. They do this by defining a requirement such as minAvailable or maxUnavailable, which controls how many pods can be evicted at once when actions like node drains or maintenance occur. For example, with three replicas and a minAvailable of 2, at most one pod can be evicted at a time, ensuring two pods continue serving traffic. This is what maintains continuity during maintenance windows. Enforcing a maximum pod count isn’t the goal of a Pod Disruption Budget, and network policies govern access between pods and services rather than pod eviction behavior. Resource quotas control total resource usage in a namespace, not how many pods can be disrupted during voluntary actions.

Pod Disruption Budgets focus on keeping services available during voluntary disruptions by guaranteeing a minimum number of pods stay running. They do this by defining a requirement such as minAvailable or maxUnavailable, which controls how many pods can be evicted at once when actions like node drains or maintenance occur. For example, with three replicas and a minAvailable of 2, at most one pod can be evicted at a time, ensuring two pods continue serving traffic. This is what maintains continuity during maintenance windows.

Enforcing a maximum pod count isn’t the goal of a Pod Disruption Budget, and network policies govern access between pods and services rather than pod eviction behavior. Resource quotas control total resource usage in a namespace, not how many pods can be disrupted during voluntary actions.