Skip to content
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

After helm uninstall spiderpool, spiderpool-init pod remains. #3960

Closed
ty-dc opened this issue Aug 27, 2024 · 1 comment · Fixed by #3925
Closed

After helm uninstall spiderpool, spiderpool-init pod remains. #3960

ty-dc opened this issue Aug 27, 2024 · 1 comment · Fixed by #3925
Assignees
Labels

Comments

@ty-dc
Copy link
Collaborator

ty-dc commented Aug 27, 2024

Spiderpool Version

latest

Bug Type

Installation Issue

Main CNI

any

What happened?

In #3811, spiderpool-init was changed from Pod to job, and the "helm.sh/hook": post-install function was enabled. However, after the function was enabled, after the job was completed, it would not be deleted with helm uninstall because its default deletion mechanism was "helm.sh/hook-delete-policy": before-hook-creation. As a result, the uninstallation of spiderpool left residue.

What did you expect to happen?

succeed

How to reproduce it (as minimally and precisely as possible)

helm install
helm uninstall

Additional Context

No response

@ty-dc
Copy link
Collaborator Author

ty-dc commented Aug 27, 2024

[root@controller-node-1 ~]# kubectl get po -n kube-system | grep spider
spiderpool-init-c76k2                       0/1     Completed   0                 39m

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant