I have a scenario where 2 charts installed via helm both think they own identically named resource (f.ex. secret), which generally isn't a problem until you want to helm delete one of them.

Lets take a simple example: Chart dingo has a Secret named db-access and then later a new cool chart named baby is created, which also happens to have a Secret named db-access. Both are in the same namespace.

helm status on both of the releases tells me they have db-access however when I run helm delete --purge dingo I do not see the db-access after running helm status baby, it is as if the dingo ate the baby resource... so to speak.

What is the expected behaviour and potential fixes?

Few things come to mind:

• Only remove resources that are not in other releases
• Installation fails if there are identically named resources (of the same resource type) in a different release
• A flag (or flags) to support either or both of the above scenarios, or the inverse