Issue: Bug report

[OferRavid]

There is a problem in the order in which the charts are being deleted.

The order of chart releases deletion is determined by the order of namespaces, which is determined by the command to get namespaces in line 100 (which as far as I can tell is alphabetical order), and then in each namespace by the order of releases in the list helm_charts, that is created in line 105 (probably also alphabetical), but that can become problematic if release 'a' is in that order before release 'b' but 'b' is dependent on 'a', because after 'a' is deleted 'b' cannot be deleted.

For example:
The chart for cert-manager defines the resource clusterIssuer so any chart that uses that resource can't be deleted after cert-manager, instead you get this error message: " Error: uninstallation completed with 1 error(s): unable to build kubernetes objects for delete: unable to recognize "": no matches for kind "ClusterIssuer" in version "cert-manager.io/v1". "

Edit:
In fact the release is deleted but the resources aren't.

[BarelElbaz]

Our plugin uses the helm native delete command/functionallity. We can try to fix it but it may be a little bit hard.

take a look here (this is the official helm repo)
helm/helm#8413

I think this behavior is specific to Crds but we should do some tests.

[Whitehawk2]

I'll be adding this to our TODO list, but like Barel said - this seems to be a "feature" or shortcoming of the native helm delete functionallity.

@BarelElbaz - On V2, maybe see if there's a way to find dangling CRDs (and delete them)?

[Whitehawk2]

since this is more if a Helm thing, I think we won't work on this (for now!)?

[BarelElbaz]

you are right.