i m using helm v3 Release and trying to upgrade postgres ope

Question

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

worried-city-86458 · Answer

Manage the crd separately via a `ConfigGroup`

square-car-84996 · Answer

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

worried-city-86458 · Answer

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

worried-city-86458 · Answer

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

worried-city-86458 · Answer

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