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

Hello all.  I have some questions about `pulumi destroy`, or how I would like to see it be more robust.  Basically right now I had a stack with an eks-cluster, and installing istio into a namespace.  The issue is when I did destroy, Kubernetes was getting hung up terminating the Istio namespace...  and because of that pulumi wouldn't continue.  First thing, I would like to see is that Pulumi can recognize these dependencies, and if I am destroying the whole stack, dont even bother trying to destroy the namespace when I am destroying the whole EKS cluster anyways... or at least give me a way to ignore issues like this and keep going

<@UH52500AG> Are you creating the name space outside of pulumi ?