https://pulumi.com logo
#kubernetes
Title
# kubernetes
s

square-car-84996

04/29/2022, 2:09 PM
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?
w

worried-city-86458

04/30/2022, 12:06 AM
Manage the crd separately via a
ConfigGroup
s

square-car-84996

05/09/2022, 2:55 PM
is there a way to migrate from helm managed CRD to ConfigGroup managed CRD without removing the installed CRDs?
w

worried-city-86458

05/09/2022, 8:48 PM
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)
7 Views