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

eager-pizza-63649

08/07/2023, 2:25 PM
Hello, I'm trying to migrate chart installation from
v2.Chart
resource to
v3.HelmRelease
. For that I patch K8s objects belonging to
v2.Chart
with Helm annotation and labels to make Helm to takeover existing manifests, but I also want Pulumi to remove corresponding Pulumi resources from the state, but keep K8s ones in a cluster. I tried to use
RetainOnDelete
option for that but Pulumi marks only
v2.Chart
resource with it, not descendants, and I don't know whether it's a bug or because chart resource is a custom component under the hood. As a result, after successful manifests takeover by Helm, Pulumi tries to delete from the cluster everything what belonged to chart resource. So is there any other option I can use to keep K8s resources in such situation, except
pulumi state delete
and direct state modification?
2 Views