eager-pizza-63649
08/07/2023, 2:25 PMv2.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?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.
Powered by