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

<@UGGR2EYP3> Pulumi doesn’t automatically update, but you likely have `@pulumi/kubernetes` set to `latest` in your `package.json` if you’re seeing different behavior now.

There’s currently no way to opt out of that label for any resources created by pulumi. Curious why you want/need that?

I didn't want to update all my deployments / daemonsets, as that would recreate all child pods, afaik.

I also think I found the "issue" - the older project had `@pulumi/kubernetes` 0.20.1, and meanwhile I created another one, which installed 0.20.3, and added the newer plugin version in `~/.pulumi/plugins`. So I was running `pulumi` in the older project, but it was using the newer version of the plugin.

Adding that label shouldn’t affect running workloads. You can check the preview diff to see what changes are expected. `pulumi preview --diff`

FWIW, here’s a link to the relevant docs on recommended labels: <https://kubernetes.io/docs/concepts/overview/working-with-objects/common-labels/#labels>

Are you sure? I know for sure that changing annotations recreates child pods, so I somehow thought changing labels has the same effect.

AFAIK, both annotations and labels in general are just metadata that you can change without further effect. There are cases where a controller acts on a specific label/annotation, e.g., updating Ingress settings, but that’s not the usual case. Would be very interested to see it if you have a counter example.

Yeah, sorry, I used annotations in the past (using helm :slightly_smiling_face: ) to restart pods in a deployment when a configmap changes, but it was actually `.spec.template.annotations`.

So I was under the wrong impression that changing annotations on a deployment also updates the pods.

Thanks for clearing that up! :slightly_smiling_face:

Great! You had me a little worried there for a second, and I had to double-check to make sure I wasn’t crazy :stuck_out_tongue:

Btw, thanks for this amazing tool, it's everything I ever needed to manage kubernetes - especially that I come from a JS/TS background! :smile: