I’ve been running a few tests with different deploys and the last couple times I ran into an issue when deleting the entando namespace. I had run into IP issues (separate story - this is due to restarting my laptop and on windows 10 that currently results in new IP assignments thanks to hyper-v) which may or may not be related. At any rate the entando namespace wound up stuck in Terminating status and this post wound up being a quick fix - https://medium.com/@clouddev.guru/how-to-fix-kubernetes-namespace-deleting-stuck-in-terminating-state-5ed75792647e