This message was deleted.

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 🧐

code never lies 🙂

yup, update is there. Ty @brash-gigabyte-81569

no prob