Deleting app instance with same app name but different Kinds

[devdattakulkarni]

We have seen the following situation happen.

There are two kinds created in a cluster - say KindA, KindB.
We create application instance for KindA, name it - appA
We delete the namespace corresponding to the appA instance using kubectl delete ns appA, without deleting the app instance itself.
We then create application instance for KindB and name it - appA.
KubePlus now creates the Namespace appA again.
Then, we realize that we have a dangling appA instance. So we kubectl delete KindA appA.
This causes the new appA namespace, which now corresponds to the appA instance for KindB, to get deleted. The helm release for appA instance for KindB also gets deleted.

This is a bug as the new appA namespace does not belong to KindA. So when we delete KindA appA, it should just delete the
appA object, without deleting the release or the namespace.

[devdattakulkarni]

This will be implemented in helm-pod.
Specifically, in line 340, we need to parse the kind name from the helmrelease variable, compare it with the kind that is passed in (line 279); if they match, then call the go func() to perform the delete action.
helmrelease has following structure: <instance-name>:<lower-case-kind>-<instance-name>
See here and
here
In order to parse kind name from the helmrelease var, String split helmrelease, first on ":", then the second part on "-". From the second split, collect all the parts except the last part.
When comparing the kind name, be sure to convert it into lower case.