+++ This bug was initially created as a clone of Bug #1800315 +++
+++ This bug was initially created as a clone of Bug #1800314 +++
Deleting the Node object in Kubernetes signals to the cluster that no pod on that node is running and that it is safe to release any storage or process locks that ensure two processes can't be running on different nodes with the same name or volumes. The machine controller was deleting the node before the machine was fully terminated, which means that a stateful set controller would be able to launch two pods with the same name running on the cluster at the same time, which violates our cluster safety guarantees.
Fix is to wait for machine is confirmed shut down by cloud provider before deleting the Node object.