# GKE node upgrade stuck: PodDisruptionBudget blocks the drain

**Code:** `PDB` · **Category:** Google Cloud / Firebase · **Seen on:** Google Cloud, Kubernetes

A cluster or node pool upgrade stalls because a PDB doesn't allow evicting the pods on the node.

## Meaning

GKE respects PDBs for up to an hour during upgrades. Relax overly strict PDBs (`minAvailable: 100%`, single replica with `minAvailable: 1`), add replicas, or temporarily patch the PDB. Check `kubectl get pdb -A` for `ALLOWED DISRUPTIONS = 0`.

## Common causes

- PDB with `ALLOWED DISRUPTIONS 0`
- Single-replica deployment with minAvailable 1
- Pods stuck terminating
- Orphaned PDB selecting nothing
- Too-strict maxUnavailable

## Quick fix

1. `kubectl get pdb -A`
2. Increase replicas or loosen the PDB
3. Delete/patch the blocking PDB temporarily

## Detailed fix by platform

### Shell

1. 

```bash
kubectl get pdb -A
kubectl get pods -A -o wide | grep NODE_NAME
```


## How to diagnose

1. **Allowed disruptions** — 0?
2. **Replicas** — More than 1?
3. **Pods** — Terminating?

---
Source: [WhatIsMyError](https://whatismyerror.com/errors/gcp/gke-pdb-blocks-node-drain-upgrade)
