This message was deleted.

sparse-intern-71089

12/08/2021, 10:01 PM

This message was deleted.

billowy-army-68599

12/08/2021, 10:07 PM

can you clarify a bit more what workflow you're using?

wonderful-twilight-70958

12/08/2021, 11:39 PM

Doing exactly this, haven't hit too many issues (raw kube and helm). Also happy to help :)

mammoth-airline-91759

12/09/2021, 1:23 PM

Two similar scenarios: 1. Deploying a Helm chart, I changed some values passed into the chart after it had been deployed. When I re-run

pulumi up

it partially fails, b/c it tries to re-create the deployment instead of just applying over top. 2. Using

k8s.yaml.ConfigFile

, I deployed several resources. Then, I changed the provider to target a different namespace, which now causes some failures b/c pulumi tries to re-create Cluster-scoped resources instead of ignoring or just applying overtop. I guess those are a bit more nuanced scenarios than I was originally thinking. 🙂

wonderful-twilight-70958

12/09/2021, 2:01 PM

Are you using chart or release for 1?

wonderful-twilight-70958

12/09/2021, 2:01 PM

I'm using Release and that use case works fine for me.

mammoth-airline-91759

12/10/2021, 5:34 AM

Remote Chart for 1

mammoth-airline-91759

12/10/2021, 5:35 AM

I saw the Release option, but didn’t choose it for some reason…

4 Views

Open in Slack

Previous Next

Pulumi Community

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.