Kubernetes namespace stuck in Terminating forever after 'kubectl delete namespace'. How do I find what is blocking it (finalizers) and fix it safely?

Cause: deleting a namespace deletes everything inside it, and Kubernetes waits until every object and every namespace finalizer has finished. A namespace stays Terminating when some object in it still has a finalizer whose controller is gone or failing (for example a custom resource whose operator was uninstalled first), when a pod or volume cannot be cleaned up, or when an unavailable aggregated API prevents the namespace controller from listing all resource types. Fix (best first): 1. Read the namespace status: kubectl get namespace NAME -o yaml. The status.conditions section normally names what remains or which API group could not be discovered. Also see spec.finalizers. 2. List what is left: kubectl api-resources --verbs=list --namespaced -o name, then loop kubectl get RESOURCE -n NAME --ignore-not-found over those types. Look for objects with a deletionTimestamp. 3. For each stuck object check its finalizers: kubectl get RESOURCE OBJECT -n NAME -o jsonpath='{.metadata.finalizers}'. The controller that owns that finalizer must do the cleanup. 4. Fix the owner rather than the symptom. Reinstall or repair the operator or CRD whose controller is missing so it can process the deletion. If an API service is unavailable (check kubectl get apiservices for False entries), restore it. 5. Last resort, only when you understand what the finalizer guarded and that cleanup is done or done by hand (external cloud resources, volumes, load balancers): remove that specific finalizer from that specific object. Kubernetes docs warn that forcibly removing finalizers can cause problems, because the cleanup they protect is then skipped and can leave orphaned resources. Do not blanket-strip finalizers across a namespace. 6. Next time, delete custom resources before uninstalling the operator that manages them. Verify: kubectl get namespace NAME returns NotFound, and no orphaned external resources (volumes, load balancers) remain in the cloud console. Sources: https://kubernetes.io/docs/concepts/overview/working-with-objects/finalizers/ https://kubernetes.io/docs/tasks/administer-cluster/namespaces/