-
Notifications
You must be signed in to change notification settings - Fork 193
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] KubeBlocks Uninstall - CRDs delete gets stuck #8814
Comments
Hi @gstefanoff It seems even though you uninstall addons, resources like actionssets, addons are not deleted actually.
|
Hi @shanshanying |
Hi @gstefanoff So what is the list of clusterdefinition. clusterversion, after uninstalling Addons, leftover in your env? k get addon,cd,cv,cc,bpt,actionsets and check the list of helm charts intalled in ns helm -n kb-system list |
Hi @shanshanying
|
Addons listed are not removed while uninstalling KB using 'helm unintall. To uninstall KubeBlocks, one should
Or you can use our command line tool kbcli kb uninstall --auto-approve For your case, since KB has been unisntalled and no one handles these CRs anymore. you may patch these reousrce to remove finalizers and remove them, e.g. # patch all clusterdefinition, remove finalizers
kubectl get cd -oname | xargs -I {} kubectl patch {} --type=merge -p '{"metadata":{"finalizers":[]}}'
# patch all addons to remove finalizers
kubectl get addon -oname | xargs -I {} kubectl patch {} --type=merge -p '{"metadata":{"finalizers":[]}}' replace |
I removed cc,cd,addon, crds as you advised. However, configmaps are still in the namespace. Deletes get stuck and the namespace is waiting for them to be removed. These configmaps are managed by helm btw.
Thanks. |
Hi @gstefanoff In kb 0.9, the ownership of these configmaps was transferred from cd/cv to cmpd. Please check the status of cmpd. There's a related bug has been fixed: #8188 Please show the metadata of the leftover configmap(
|
Hi @sophon-zt Here's the output
|
Describe the bug
Installed KubeBlocks (version 0.9.2 ) via helm using these instructions
When I tried uninstalling with helm, I was not able to delete CRDs. Every attempt resulted in delete processes being stuck. I am not able to delete the namespace because k8s is waiting for 23 resources to be removed, the problem is I cannot remove them either because they get stuck as well the only solution, I have not tried yet is the one mentioned here.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
KubeBlocks should be as easily removed as it is installed. Having to resort to "workarounds" such as removing finalizers is not feasible solution.
Screenshots
Not actually deleted!
Additional context
logs from kb-system namespaces pending deletion.
The text was updated successfully, but these errors were encountered: