Kuberneteskubernetespdbavailabilitymaintenanceproduction-ready

Pod Disruption Budget

Kubernetes PDB configurations for maintaining service availability during voluntary disruptions like node upgrades and cluster scaling.


title: "Pod Disruption Budget" description: "Kubernetes PDB configurations for maintaining service availability during voluntary disruptions like node upgrades and cluster scaling." category: "Kubernetes" language: "yaml" tags: ["kubernetes", "pdb", "availability", "maintenance", "production-ready"] createdAt: "2025-04-20" updatedAt: "2025-05-05"

Overview

Pod Disruption Budgets protect service availability during voluntary disruptions (node drains, cluster upgrades, autoscaler scale-down). Combined with topology spread constraints, they ensure geographic distribution and minimum replicas during maintenance.

Code

apiVersion: policy/v1
kind: PodDisruptionBudget
spec:
  minAvailable: 2          # OR
  maxUnavailable: 25%      # percentage of total replicas
  selector:
    matchLabels:
      app: my-service

Notes

  • PDBs only affect voluntary disruptions (node drain, autoscaler); not involuntary (OOM, node crash)
  • minAvailable guarantees a minimum replica count; maxUnavailable limits simultaneous disruptions
  • Use percentage for services that auto-scale (scales with replica count)
  • Use absolute numbers for critical services with fixed replica requirements
  • Topology spread constraints distribute pods across failure domains (zones, nodes)
  • PDB + anti-affinity ensures a single node failure cannot take the service offline