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'm using helm.v3.Release and trying to upgrade postgres-operator from 1.7.1 to 1.8.0, seems like their CRD changed but pulumi isn't upgrading it.  Any suggestions?

Manage the crd separately via a `ConfigGroup`

is there a way to migrate from helm managed CRD to ConfigGroup managed CRD without removing the installed CRDs?

Helm doesn't upgrade or delete crds afaik, hence managing them via a config group.
I recommend specifying both `Atomic` and `SkipCrds` to the helm release args.
Try it out somewhere safe to be sure.

Oh and specifying `EnableReplaceCRD` on the k8s provider seems to avoid issues with large crds

(Although I'm hitting another issue that the crd metadata is always updated by pulumi - I need to file another issue related to this)