-
Notifications
You must be signed in to change notification settings - Fork 132
Cannot delete kubeprod namespace #739
Comments
|
So I manually edited all those challenge resources and removed the finalizers. Then the namespace terminated and was deleted. This looks like a bug though, right? |
Generally the cleanup should work as expected, but it appears such issues can be encountered on k8s due to third party resource (cert-manager) in this case. I think this is a bug, but in not in BKPR. We should document it in the troubleshooting guide though. ref: |
The cert manager issue seems to suggest they are treating it as not their problem: "it is a symptom of not following the install/upgrade instructions, which, at this point REQUIRES uninstalling cert-manager + all CRDs and CRs". Doesn't that imply we should be able to fix this in BKPR with some more careful orchestration of tear down? |
Maybe a |
Hi, In this case, the kubeprod binary does not perform any kind of cleanup or teardown, so it is the admin that should use the proper kubectl/kubecfg commands. I believe that the best choice should be updating the documentation so it contains a "Uninstall cert-manager" is clearly mentioned. Would that make sense? |
Hit this issue as well. In case for anyone else, for each of the challenge resources listed above, had to manually edit each of them and delete the "finalizer:" key from the yaml file. Then the ns terminated. Example:
|
Hi, Thank you very much for the tips! The community will benefit from this :) |
Confirming that challenge.acme.cert-manager.io finalizers hold
|
Nothing seems to work when I want to tear down and uninstall BKPR. I followed the instructions and the step where the namespace is deleted always times out. Also tried doing that manually. Same result. The only thing that worked for me was to delete the whole cluster. This was on GKE.
Here's a clue:
The text was updated successfully, but these errors were encountered: