No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

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