In most cases, you would find out why it fails from the log itself. Find why it is taking time and check the logs of the resource to look for any clues kubernetes describe name-of-the-resource That's what we need to do in this context too. The second best recommendation is really simple and we do it in real life too, when things are stuck, we just have to find out why and unstuck/clear it. When you really feel that it has taken a more than few minutes. So the first recommendation I can give is to wait for a while. In most cases, we run out of patience with our kubectl delete and go for the kubectl patch solution we gave earlier.īut we need to understand that it has some final clean-ups to do and it takes time.įor example, When you delete ingress, you need to delete the target group and the load balancer etc before we can delete the ingress object on Kubernetes. What is the recommended way when your kubectl delete is stuck This should be manually cleaned up later or it would be there for a decade in your Infrastructure and you would be paying for it. If we do that, Kubernetes API would ignore the dependencies as it is and continue with the deletionīut of course, at the cost of leaving the dependency resource stranded, p '' – type=mergeīy doing this, we are simply resetting the finalizers or emptying it When you kubectl delete command stuck, You can execute the following command and you can see your kubectl delete command/task would be now completed ( if it was stuck at deleting) What to do when your kubectl delete stuck What is the recommended way when your kubectl delete is stuck.But why Finalizers now ? How it is related to what we did.What to do when your kubectl delete stuck.

Nups gc patcher