on my kube helm charts to skip deleting them when the EKS cluster (built with
@pulumi/eks
) is being destroyed as well. It doesn't seem to work though and pulumi still attempts to destroy the billion CRDs instead of just nuking the cluster - is it because
@pulumi/eks/cluster
is a ComponentResource? I'm not able to reference the underlying aws resource directly because it's exposed as an Output
late-balloon-24601
10/16/2024, 10:29 AM
This might have been because I hadn't explicitly done a deployment since adding the
deletedWith
statements. Will find out if that's the case this evening when I tear down the cluster again
q
quick-house-41860
10/16/2024, 11:21 AM
This should work if you run a
pulumi up
after you added the resource option. Otherwise the
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.