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

:wave::skin-tone-3:  I've a helm chart setup to be installed / updated as part of a `pulumi up`. That helm chart results in a DaemonSet and a Deployment. I'd like to trigger a rollout of the Deployment after the helm chart applies. I feel like I may be able to achieve this with Server-Side Apply, but I'm failing to see how. If anyone has any pointers I'd be very grateful !

For a little more detail; the update doesn't tend to touch the `deployment.spec.template` ; so k8s doesn't trigger the rollout for me.

The main change tends to be in annotations on service accounts; so I'm looking for something more generic like running `kubectl rollout deployment foo` as a "hook". I'm fine with it running after each apply / update in this case.

I use the local command like this example for a similar use case <https://github.com/pulumi/pulumi-command#graceful-cleanup-of-workloads-in-a-kubernetes-cluster>

thanks for the suggestion Matt, I looked at `@pulumi/command` and this stood out to me in the manual: <https://github.com/pulumi/pulumi-command/issues/20>

Specifically I feel that without `update` I can't get what I want? <https://github.com/pulumi/pulumi-command/issues/20#issuecomment-1423469227>

Have you found command to be more flexible than the docs suggest in this regard?

I used it for cleaning up k8s resources on delete but I did see an `Update` field in there and assumed it would work

neat - I'll poke now - thanks! Keen reminder to look at the code, not just the docs :face_with_monocle: