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

Because changing the metadata.name recreates a PVC. To not lose data, we ignore the whole metadata field because we don't know updates to which other metadata fields cause recreations.

Changing the name does indeed recreate a PVC, but that's the intended behaviour.  I'd suggest using `preview` to verify change sets, as ignoring the entire metadata could have unintended side effects as you've noticed.

That's not a feasible option since the up flow is automated using the automation API, so we do not preview the changes. But anyway, ignoring just the `metadata.name` has been enough to ensure that the PVC is not deleted on changes. Thank you for your input!