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

As the ALB are created out of band (by the controller in the EKS cluster) and not by pulumi I think the best thing might be to import them after creation and sort out the dependency tree so they get deleted before the subnets.

I'm just starting to do the same thing as you, so am interested in thee solution here.

I have observed the same behavior and AFAIK <@U01UELY9YUR>’s response is accurate. We’ve had to remove the load balancers first (by deleting the workloads on the cluster) and then run `pulumi destroy`. I haven’t found an automated solution yet.

<@U01UELY9YUR> Yes, this is one solution. I'm now investigating  the Automation API, so we can detect destroy event easier and based on tags into load balancer (which we get with getLoadBalancer) remove the ones we wish.

<@UJBNC99MF> Yes, delete the workload first would be a fit also. But sometimes we just one a fast cluster removal. Automation API and being able to get specific load balancers is one solution we are experimenting.

<@U03MKGMRSSX> I look forward to hearing about the results of your testing/investigation!