@gorgeous-egg-16927 I was trying to upgrade

pulumi-kubernetes

to a more up-to-date version. But my stack wasn’t able to refresh if I didn’t have the old plugin version existing on the machine (I’m running in container so I only have the recent plugin version) Other pulumi provider have this behaviour and I was wondering if this is a bug

Diagnostics:
  pulumi:providers:kubernetes (default_2_6_1):
    error: no resource plugin 'kubernetes-v2.6.1' found in the workspace or on your $PATH, install the plugin using `pulumi plugin install resource kubernetes v2.6.1`

(I was upgrading from 2.6.1 to 2.6.3)

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

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