This message was deleted.
# kubernetes
s
This message was deleted.
w
Manage the crd separately via a
ConfigGroup
s
is there a way to migrate from helm managed CRD to ConfigGroup managed CRD without removing the installed CRDs?
w
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)