i'm having an issue where, when i change the values for a helm chart that's deploying mongodb, the mongo deployment gets stuck because it's waiting for the old pod release to pvc. how would i go about fixing this? do i need to apply a transformation on the chart to modify the deployment object to give it

deleteBeforeReplace: true

?

I posted the same problem a while back, https://pulumi-community.slack.com/archives/C84L4E3N1/p1581073625074400?thread_ts=1581073625.074400. I think we need some way of grouping resources together in such a way that you can guarantee that one belongs with the other

but don't you want it to not create a new PVC? i.e. if i change some config values of a deployment that relate to how the database works, i don't want to wipe the entire database.

I don’t think it’s exactly the same problem no but they are very related. It’s about the ability to “exclusively own” a resource so that rolling updates etc are planned accordingly