Hands-on Lab·Certified Kubernetes Administrator
Troubleshooting a Namespace Stuck Terminating
A namespace held open by one object inside it. This reads the conditions, shows why they are not enough, finds the object, and is explicit about what the popular one-liner actually abandons.
Troubleshooting Guide 83 of 103 Advanced
- Kubernetes1.36.4
- Cluster4 nodes
- Runtimecontainerd 2.2.6
- CNICalico v3.32.1
- TimeAbout 16 min
The finalizer here is a made-up string with no controller. On a real cluster this is nearly always a custom resource whose operator has been uninstalled.
| 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 |
This guide includes
Use this when a namespace has been Terminating for hours. This matters because the namespace is almost never the problem - one object inside it is holding the whole thing open, and the one-liner everyone pastes fixes the symptom by abandoning the cleanup.
- creating a namespace held open by a single object inside it
- reading the five namespace conditions, and seeing why they are not enough on their own
- finding the offending object, which is the step that actually resolves it
- clearing the finalizer on that object rather than on the namespace
- seeing the dangerous shortcut everybody reaches for, and precisely why it is dangerous
Before you start
- guide 82 - the same mechanism one level down, on a single object.
-
A namespace that will not go away
-
The conditions, and why they are not enough
-
Find the object itself
-
Clear it the right way
-
The dangerous shortcut, and why it is dangerous