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

Hi <@USJJKQ4CQ>! What I would do is `pulumi stack export` to a file or to STDOUT. Then, I would look for the specific URN of the resource you want to delete and issue `pulumi destroy -t &lt;URN&gt;`

<@UN8M760CX> but my question is , why there is a dangling resources create on the first place. I was going though the console so I got to know, that something not deleted.

I do not know. I am just a pulumi user as you are. I offered you a workaround to solve your issue, but it is impossible to investigate the root cause without looking at your code. I think that any Pulumi team member would ask you to share the code as well

Don’t rely on Pulumi for destroying things. We don’t. Deletion of resources are done manually via aws console.
We rely on proper tagging and discovery for searching which resources to remove for ephemeral stacks.

If Pulumi doesn't remove something properly during a `destroy` that's a bug and we would greatly appreciate a bug report with steps to reproduce!

<@USJJKQ4CQ> in some cases it's the EKS control plane that is creating AWS resources, based on the `k8s.core.v1.Service` resource that is defined. So it might be that EKS left the ALB resources behind unfortunately.

That’s the issue of using outside stuff creating AWS resources. I wish we could set up the ALB ingress controller *and* configure it using Pulumi instead. It’s way more reliable.

<@UDEJ1F5SQ> - I have not run `destroy`  command. I simply remove code and did `pulumi up`  and later added modified code.