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

pulumi just interacts with the Kubernetes api, so I'd be surprised if this was pulumi specific...

if you're doing a pulumi up with a new image, it'll just update the deployment with the new image via the API, the rest happens at the kubernetes layer

I actually ended up filing an issue on github as well and found the root cause (not related to pulumi). Details can be found at <https://github.com/pulumi/pulumi/issues/7330>

looks like 'dumb-init` will help with that, fyi

oh nice, that seems perfect, will give it a shot today. Thanks for the pointer :slightly_smiling_face: