I have seen namespaces in Kubernetes get stuck from time to time too and never really understood why. My workaround is usually to follow the steps from https://craignewtondev.medium.com/how-to-fix-kubernetes-namespace-deleting-stuck-in-terminating-state-5ed75792647e
1) kubectl get namespace mynamespace -o json > mynamespace.json
2) Remove "kubernetes" from the finalizers array
3) kubectl replace --raw "/api/v1/namespaces/mynamespace/finalize" -f ./mynamespace.json
Could juju skip the phase to wait for the namespace deletion if --force is specified to destroy-model?
I have seen namespaces in Kubernetes get stuck from time to time too and never really understood why. My workaround is usually to follow the steps from https:/ /craignewtondev .medium. com/how- to-fix- kubernetes- namespace- deleting- stuck-in- terminating- state-5ed757926 47e
1) kubectl get namespace mynamespace -o json > mynamespace.json
2) Remove "kubernetes" from the finalizers array
3) kubectl replace --raw "/api/v1/ namespaces/ mynamespace/ finalize" -f ./mynamespace.json
Could juju skip the phase to wait for the namespace deletion if --force is specified to destroy-model?