Hands-on Lab·Certified Kubernetes Administrator
Troubleshooting Pod Terminating
A delete that returns successfully and leaves the object behind. This separates the two causes that look identical for the first thirty seconds - a finalizer nobody owns, and a container that will not take a signal.
Troubleshooting Guide 82 of 103 Intermediate
- Kubernetes1.36.4
- Runtimecontainerd 2.2.6
- CNICalico v3.32.1
- TimeAbout 18 min
- Reviewed26 August 2026
Written against the versions above. The 30 second wait is `terminationGracePeriodSeconds` at its default. Timings here are from a real delete and will vary by a second or two.
| Server Name | IP Address | OS | Roles | CPU | RAM | HDD |
|---|---|---|---|---|---|---|
| CKA1001 | 192.168.0.175 | Ubuntu 26.04 LTS | Control Plane Node | 2 Core | 4 GB | 50 GB |
| CKA1001-NODE01 | 192.168.0.176 | Ubuntu 26.04 LTS | Worker Node | 2 Core | 4 GB | 50 GB |
| CKA1001-NODE02 | 192.168.0.177 | Ubuntu 26.04 LTS | Worker Node | 2 Core | 4 GB | 50 GB |
| CKA1001-NODE03 | 192.168.0.178 | Ubuntu 26.04 LTS | Worker Node | 2 Core | 4 GB | 50 GB |
Before you start
- guide 36 - where the grace period sits in a Pod's shutdown.
-
A Pod that will not delete
-
What is actually holding it
-
Wait past the grace period, and watch the symptom change
-
Who is supposed to clear it, and clearing it by hand
-
The other reason a delete looks slow, which is not this