# Helm uninstall leaves orphaned ingress

**URL:** <https://forum.rasa.com/t/helm-uninstall-leaves-orphaned-ingress/28148>\
**Category:** \[Deprecated\] Rasa X Community Edition\
**Created:** [April 28, 2020, 1:50pm UTC](https://forum.rasa.com/t/helm-uninstall-leaves-orphaned-ingress/28148 "2020-04-28T13:50:35Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![cck197](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.rasa.com/cck197/32/7901_2.png) [@cck197](https://forum.rasa.com/u/cck197)\
**Post date:** [April 28, 2020, 1:50pm UTC](https://forum.rasa.com/t/helm-uninstall-leaves-orphaned-ingress/28148/1 "2020-04-28T13:50:35Z")

</div>

Say you want to uninstall the helm chart, and you run a command like `helm uninstall rasa-x-1586547433` It works, but the ingress servers get left behind, like this:

 ![image](https://europe1.discourse-cdn.com/flex013/uploads/rasa/original/2X/2/267d2f13758a52f871f35bf05ad71f1cf392c7e6.png)

`kubectl delete --cascade=true ingress rasa-x-1586547433` will [hang](https://github.com/kubernetes/kubernetes/issues/60066#issuecomment-432553546), waiting for the dependant resource to get deleted.

The command `kubectl patch ingress rasa-x-1586547433 -n rasa -p '{"metadata":{"finalizers":null}}'` fixes the problem, and now the delete command returns successfully.

Hopefully, this post saves someone the time I spent yesterday figuring this out!