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

I seem to still be having some _very_ weird issues from the k8s auto-aliasing change (previously mentioned here <https://pulumi-community.slack.com/archives/C84L4E3N1/p1570297147325000>)

Here’s a super simple example where I”m seeing weirdness:
<https://gist.github.com/timmyers/adc57e4dca7dc7a3c14a310d5f4ce6a6>

The program consists of a namespace and a deployment.  I have those both applied successfully, `pulumi up` shows no diff.  Then I uncomment the service object and try to  `pulumi up` again.

The first run crashed, the second one gives a very odd unexpected diff.

Can you open an issue pointing at this gist? Definitely want to look into this.  cc also <@UE1LN7A22>.

Yeah of course.  Let me know what other info I can try to grab.  I’m having weird issues like this on every stack, I must have something weird going on with my environment or something if no one else is hitting this.

<https://github.com/pulumi/pulumi-kubernetes/issues/849>

Fix is in progress: <https://github.com/pulumi/pulumi-kubernetes/pull/850>

Fix has merged to master, so you can try it out with <https://www.npmjs.com/package/@pulumi/kubernetes/v/1.3.0-alpha.1571265977> (`@pulumi/kubernetes:dev`)

<https://github.com/pulumi/pulumi-kubernetes/releases/tag/v1.2.3> is out now with this fix