GKE node upgrade stuck: PodDisruptionBudget blocks the drain
A cluster or node pool upgrade stalls because a PDB doesn't allow evicting the pods on the node.
Cannot evict pod as it would violate the pod's disruption budgetnode pool upgrade stuck PodDisruptionBudgetGKE upgrade blocked by PDBEviction would violate the pod's disruption budgetPodDisruptionBudget drain 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
kubectl get pdb -A- Increase replicas or loosen the PDB
- Delete/patch the blocking PDB temporarily
Detailed fix by platform
Shell
- bash
kubectl get pdb -A kubectl get pods -A -o wide | grep NODE_NAME
How to diagnose
- Allowed disruptions — 0?
- Replicas — More than 1?
- Pods — Terminating?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
- Autopilot GKE Autopilot rejected the workload: resources adjusted / violates Autopilot constraints
- FailedScheduling Kubernetes: Pod stuck in Pending — FailedScheduling: 0/3 nodes are available
- GKE Ingress: backends marked UNHEALTHY (502) GKE Ingress: Some backend services are in UNHEALTHY state / 502 Server Error from the load balancer
Most viewed in Google Cloud / Firebase
- Missing or insufficient permissions Firestore: FirebaseError: [code=permission-denied]: Missing or insufficient permissions
- Container failed to start Cloud Run: The user-provided container failed to start and listen on the port defined provided by the PORT=8080 environment variable
- 409: The resource already exists Compute Engine: ERROR: (gcloud.compute.instances.create) Could not fetch resource: The resource 'projects/p/zones/z/instances/vm-1' already exists
Other ways to find it
Where this error sits
Origin: Platform & cloud. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Report a correction or suggest an improvement
Last updated 18 Nov 2026