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

After that, I deleted the cluster manually in AWS, and tried to use `pulumi destroy` to clean up the miscellaneous other objects... but Pulumi again choked on removing the namespace, because now it couldn't talk to the cluster.  I would like to see Pulumi be smarter here, recognize the cluster is gone so the dependent objects are also gone and help me remove the miscellaneous other objects.

<@UE1LN7A22> should we create an issue for this as well, as it is a slightly different problem?

actually this looks like it is the same as this second aspect <https://github.com/pulumi/pulumi-kubernetes/issues/416>