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

My route forward is to create the PV and PVC before the helm release and then use a feature of this chart which allows me to specify an existing PVC for use for grafana's persistence. I can then set `retainOnDelete` on it and it should be safe.

However this doesn't resolve the bigger issue with CRDs not being updated by helm and major version upgrades of helm charts which use them requiring special attention to run CRD updates which seem hard to automate, and destined to break your deployed monitoring stack if you're not careful.

yes, definitely pin all the chart versions!!

once you have them pinned, it sounds like it might be pretty simple to do these types of upgrades. you could add the CRDs using <https://www.pulumi.com/registry/packages/kubernetes/api-docs/yaml/configfile/>