> For the complete documentation index, see [llms.txt](https://mifos.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mifos.gitbook.io/docs/payment-hub-ee/overview/uninstallation-instructions.md). # Uninstallation Instructions Uninstall the helm chart from a specific Namespace Helm uninstall removes all of the resources associated with the last deployed chart as well as the deployment history. ``` helm uninstall RELEASE_NAME -n ``` Note: here The helm uninstallation may not delete the persistent volume. in that case, it can be deleted by using the command 
kubectl get pv
kubectl delete pv <pv_name> --grace-period=0 --force
However, sometimes the cluster resources are not deleted, in such cases, we highly recommend deleting the Namespace from the cluster for a new deployment. as this will delete all the resources attached to the previous deployment in that particular namespace. ``` kubectl delete namespace [your-namespace] ``` To Delete the cluster-role and cluster-role-bindings ``` kubectl delete clusterroles kubectl delete clusterrolebinding ``` --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://mifos.gitbook.io/docs/payment-hub-ee/overview/uninstallation-instructions.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.