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

If you created the namespace with Pulumi, Pulumi should not be attempting to re-create it.

Pulumi keeps track of your resources in different stacks (<https://www.pulumi.com/docs/intro/concepts/stack/>) which is how Pulumi remembers the resources that have been created. If you create a namespace in one stack, then `pulumi stack init ...` a new stack, Pulumi will not be aware of the existing namespace in that new stack.

Is it possible you changed the stack you're acting on?

If you run `pulumi stack`, do you see the `Namespace` resource?

Well aware of that, and it was most likely due to the `provider` being omitted from some of the commands, so the stack got confused as to the real target when I added the provider to all the resource requests. In any event, it would be nice to perhaps have an `importIfExists`  option for kubernetes stuff - there likely won't be any full-fledged ID that would be pulled out, but I know there's some discussion still ongoing for `patch`vs `apply` vs `create` operational methods