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

It would be hard to run `kubectl` directly, because we don’t generate YAML? Unless I’m missing something?

Because resources can have dependencies, so, we need to order them.

_e.g._, you must create a `Service` before you create a `StatefulSet`.

oh, I would use pulumi to set it up initially (outside of CI) and then use kubectl to change the image of the deployment

But it sounds like I should instead pipe the image sha in via config and have CI run a pulumi up?

I think I do not understand. :slightly_smiling_face:

why not just declare the image you want inside the pulumi program?

Hrm, maybe I am missing something. So when I deploy, I tell it to use some image

Then when CI runs again, it uploads a new image

is this not just a PR that changes an image tag?

I want this to happen on every commit as part of merging to master

Hmm, so the app code is in the same directory as the pulumi code?

And you’re saying you’re doing a `docker build -t tberman/whatever:v0.3.0 ... &amp;&amp; docker push ...` and you _also_ want pulumi to update using that new  tag

yeah, I am using jib to create and push the builds (its a maven plugin), but the same idea applies

That part shouldn’t matter, I have the images going into gcr

so whatever tag your using, as part of your build target, just run a `pulumi set config appImageTag $TAG` or something