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.

Pulumi Community

can you elaborate? you’re destroying the cluster so you don’t want bother deleting the helm release?

Exactly.
There wont be any service of loadbalancer type, so nothing externally created.

And the ec2-instances where everything is running will be deleted. So feels a bit iffy to wait for uninstalls since sometimes kubernetes namespaces or pods gets stuck in Terminating state that needs manual patching of the finalizers to get rid of

Try setting `retainOnDelete` on the resource provider: <https://www.pulumi.com/docs/intro/concepts/resources/options/retainondelete/>

it’ll just get removed from state, but the resource gets left alone

Usecase: automatic setup / teardown of environments for tests in our platform team