Authors: Aaron Alpar (Kasten)
Deleting objects in Kubernetes can be challenging. You may think you’ve deleted something, only to find it still persists. While issuing a kubectl delete command and hoping for the best might work for day-to-day operations, understanding how Kubernetes delete commands operate will help you understand why some objects linger after deletion.
In this post, I’ll look at:
What properties of a resource govern deletion How finalizers and owner references impact object deletion How the propagation policy can be used to change the order of deletions How deletion works, with examples  For simplicity, all examples will use ConfigMaps and basic shell commands to demonstrate the process.

oc delete project dev --force --grace-period=0 does not completely delete a project "I am unable to delete a project" The project is stuck in "Terminating" stage after deletion