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

Running `pulumi about` should give details on dependencies.
4.5.0 was yanked (release removed), updating to 4.5.1 should fix the plugin

You've mentioned 2 ways of managing python dependencies here, requirements.txt and pyproject.toml.
Which are you trying to use to run pulumi?

Looks like delete the whole venv and do `pip install requirements.txt` do the trick.

But am I doing this right? I feel like I lock myself to one plugin version. Because if I ever to update the plugin version. It’ll replace everything on my cluster.

Are there any best practice doing this?

My understanding of the issue is that it's the preview being over-cautious.

To play it safe, you can do `pulumi up --target 'provider urn'; pulumi refresh`

It's a known issue, something on Pulumi's radar

Thank you very much, I’ll try this. Is there an issue about this on github that I could follow?

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