Velero Uninstall: Velero namespace stuck in "Terminating" state #8379
Replies: 3 comments 2 replies
-
kubectl get ns velero -oyaml |
Beta Was this translation helpful? Give feedback.
-
@kaovilai, thank you for your response. I executed
I also tried to install Velero by following the procedure outlined in this documentation: |
Beta Was this translation helpful? Give feedback.
-
@kaovilai, thank you for your response. I really appreciate your help! The issue has been resolved. It turns out the problem was that there were no worker nodes, which caused it to get stuck in the "Terminating" state. |
Beta Was this translation helpful? Give feedback.
-
Hello everyone,
After uninstalling Velero, all resources were deleted, but the Velero namespace is stuck in a "Terminating" state. Has anyone encountered this before? If so, could you please share any solutions or workarounds that worked for you? I tried manually deleting the namespace with some commands, but it didn't work.
Velero version: v1.14.1
I tried these commands, but they didn't work:
velero uninstall
kubectl delete namespace velero --grace-period=0 --force
kubectl get ns velero -o json | jq '.spec.finalizers = []' | kubectl replace --raw "api/v1/namespaces/velero/finalize" -f -
Thank you in advance for your help!
Beta Was this translation helpful? Give feedback.
All reactions