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

This definitely smells like a bug to me (cc <@UBAJ7TD53>). Do you mind filing an issue? Based on the discussion in <https://github.com/pulumi/pulumi-kubernetes/issues/231>, I have a feeling `Read` is going to get a revamp in the coming week or so (which is what `refresh` depends on).

ofc, opened up here: <https://github.com/pulumi/pulumi-kubernetes/issues/234>

<@UD2HJDBCL> <@U84SY03DF> bad news is that it’s a bug, good news is that I already have a fix for it.

Basically, we implemented `read` and tests for service specifically, but failed to actually connect the read logic to the provider. :face_with_rolling_eyes:

I noticed it independently yesterday and was planning to include it with the fixes in read generally.

<@UD2HJDBCL> Technically M18 closes the friday after this coming friday, but I am planning to have the pulumi-kubernetes RC either later this week, or early next.

oh right we’re on 0.17. I was thinking 0.15

This will actually be pulumi-kubernetes v0.18.0, because of some breaks in the Helm API.

Eventually that will probably be pulled out into its own package.

<@UD2HJDBCL> your bug fix is in flight, will land with PR #230