Skip to content

Pod Disruption Budget configuration

A Pod Disruption Budget (PDB) configuration allows users to define constraints on the voluntary disruption of pods in a Kubernetes cluster to ensure application high availability.^[400-devops-06-kubernetes-devops-helm-terraform-helm-helm-charts-metrics-server-readme.md]

Configuration Parameters

When configuring a PDB (often within a Helm chart values.yaml), the primary control is the enabled switch.^[400-devops-06-kubernetes-devops-helm-terraform-helm-helm-charts-metrics-server-readme.md] If set to true, a PodDisruptionBudget resource is created.^[400-devops-06-kubernetes-devops-helm-terraform-helm-helm-charts-metrics-server-readme.md]

To specify the desired level of availability, you can configure one of two mutually exclusive parameters^[400-devops-06-kubernetes-devops-helm-terraform-helm-helm-charts-metrics-server-readme.md]:

  • minAvailable: This parameter defines the minimum number of instances (or percentage) that must remain available during a disruption^[400-devops-06-kubernetes-devops-helm-terraform-helm-helm-charts-metrics-server-readme.md].
  • maxUnavailable: This parameter defines the maximum number of instances (or percentage) that can be unavailable during a disruption^[400-devops-06-kubernetes-devops-helm-terraform-helm-helm-charts-metrics-server-readme.md].

These settings are ignored if the creation of the PodDisruptionBudget is disabled^[400-devops-06-kubernetes-devops-helm-terraform-helm-helm-charts-metrics-server-readme.md].

Sources

  • 400-devops-06-kubernetes-devops-helm-terraform-helm-helm-charts-metrics-server-readme.md