Configure PodDisruptionBudget unhealthyPodEvictionPolicy to unblock node drains with already-unhealthy pods

domain: kubernetes.io · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Set spec.unhealthyPodEvictionPolicy: AlwaysAllow in the PodDisruptionBudget manifest (policy/v1), alongside the existing minAvailable or maxUnavailable field.
  2. Confirm the target cluster is 1.27+ (field is beta and enabled by default) or 1.29+ (field is GA/stable) so no feature gate needs to be toggled; the field was added as alpha in 1.26.
  3. Apply with kubectl apply -f pdb.yaml and verify with kubectl get pdb <name> -o yaml that .spec.unhealthyPodEvictionPolicy shows AlwaysAllow.
  4. Re-run kubectl drain <node> --ignore-daemonsets --delete-emptydir-data; the drain's Eviction API calls can now evict Pods that are Running but not Ready, instead of blocking until status.currentHealthy >= status.desiredHealthy.
  5. Leave unhealthyPodEvictionPolicy unset (default IfHealthyBudget) on PDBs guarding quorum-sensitive apps (etcd, ZooKeeper) where evicting an already-unhealthy replica mid-outage could break quorum.

Known gotchas

Related routes

Configure a Kubernetes PodDisruptionBudget to protect a stateful application during node drain and rolling upgrades
kubernetes.io · 5 steps · unrated
Configure a PodDisruptionBudget to protect a workload during voluntary disruptions
kubernetes.io · 5 steps · unrated

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans