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

``` +  kubernetes:core:Namespace ingress creating Retry #0; creation failed: namespaces "ingress" already exists
 +  kubernetes:core:Namespace ingress creating error: Plan apply failed: namespaces "ingress" already exists
 +  kubernetes:core:Namespace ingress **creating failed** error: Plan apply failed: namespaces "ingress" already exists```

i've had that on a brand new cluster that only pulumi's touched, somehow i think it created a namespace but errored before it got put in the stack file

scratch that - was related to ambient providers again.

though neither `kubectl config get-contexts` and `kubectl config get-clusters` list anything so i'm not sure how it had decided it already existed... is that the generic error message for namespaces if creating fails?