KubernetesSenior
Pod stuck in Terminating
A pod stuck in Terminating usually has a finalizer that an admission webhook prevents the control plane from removing. Find the webhook and fix it.
What you see
- A deleted pod stays in
Terminatingand does not go away
What it means
A deletion was issued, but the control plane cannot remove the Pod object. The Kubernetes docs say this is usually a finalizer combined with an admission webhook that blocks the update which would remove the finalizer.
How to confirm the cause
- 1Look for finalizers on the pod
kubectl get pod POD_NAME -o yaml
Check
metadata.finalizersandmetadata.deletionTimestamp. - 2List webhooks that could be involved
kubectl get validatingwebhookconfigurations,mutatingwebhookconfigurations
Look for any that target
UPDATEoperations onpods.
Causes and fixes
A webhook rejects the UPDATE that removes the finalizer
- HOW TO TELL
- A Validating or MutatingWebhookConfiguration targets
UPDATEonpods. - FIX
- If a third party provides it: use the latest version, disable the webhook for
UPDATEon pods, or report an issue to the provider. If you wrote it: a mutating webhook must never change immutable fields onUPDATE, and a validating one should apply policies only to new changes so pods with existing violations can still pass.
How to stop it coming back
- Test admission webhooks against pod updates and deletes, not only creates.
- Use
failurePolicyand timeouts deliberately for webhooks that match core resources.
Keep going
- Runbook: Pods evicted by node pressure (MemoryPressure, DiskPressure, PIDPressure)
- Cheat sheet: kubectl
- Lesson: the kubernetes topic in Learn
Sources
Kubernetes documentation (kubernetes.io), read 18 Nov 2026. The docs version selector listed v1.33 to v1.37.