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 believe this is expected behavior. The `refresh` will use the last used plugin version until an `update` occurs with a newer plugin version.

This doesn’t happen in aws and azure plugins

I’d expect plugins should have some backwards compatibility integrated within them

<@UDEJ1F5SQ> I’m sorry for bringing this again, but `pulumi-kubernetes` is the only plugin so far that behaves this way.

I’m using azure-nextgen, gcp, aws, tls and random and none of them behaves this way.

That is strange. Could you open an issue at <http://github.com/pulumi/pulumi-kubernetes|github.com/pulumi/pulumi-kubernetes> with steps to reproduce?