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.

Sign up for GitHub

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

Jump to bottom

Uninstall processes #48

Closed
zhaosimon opened this issue Jun 24, 2022 · 1 comment
Closed

Uninstall processes #48

zhaosimon opened this issue Jun 24, 2022 · 1 comment
Labels
kind/documentation Categorizes issue or PR as related to documentation.

Comments

@zhaosimon
Copy link
Member

I could not find the uninstall processes in ReadMe, not sure if there is or not?

It is necessary sometimes to remove all the hwamei components completely for testing purpose.
@SSmallMonster SSmallMonster added the kind/documentation Categorizes issue or PR as related to documentation. label Jul 14, 2022
@SSmallMonster SSmallMonster transferred this issue from another repository Jul 14, 2022
angel0507 pushed a commit to angel0507/hwameistor that referenced this issue Jul 18, 2022
@sun7927
Merge pull request hwameistor#48 from sun7927/lvm
0c49af8 
clean the unused code and keep the LVM volume only
@SSmallMonster
Copy link
Member

@zhaosimon The system can be uninstalled through helm uninstall hwameistor. However, relevant resources will not be deleted.

Therefore, if you want to delete them completely, you need to know whether the resources below are used by the upper application. This process may be more complex and cautious.

After confirming that it is not used, you can delete the relevant resources (you can see the resource definition through kubectl API resources | grep hwameistor)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/documentation Categorizes issue or PR as related to documentation.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@SSmallMonster @zhaosimon