Instead of having to check a namespace in Terminating phase to find out which resources are causin troubles, the kubectl-terminate could do it for us, if the Go client is able to get all resources (not only pods, deployments, etc.) that belong to a namespace. Then it would only be a matter of removing the finalizers on these child resources and delete them afterwards.
Instead of having to check a namespace in
Terminatingphase to find out which resources are causin troubles, thekubectl-terminatecould do it for us, if the Go client is able to get all resources (not only pods, deployments, etc.) that belong to a namespace. Then it would only be a matter of removing the finalizers on these child resources and delete them afterwards.