https://pulumi.com logo
Title
m

mammoth-airline-91759

12/08/2021, 10:01 PM
Are other folks here using Pulumi to manage a few kubernetes resources? When bringing up a new stack, it seems like Pulumi would be a good place to install some prerequisites prior to our CD pipeline taking over. However, if I ever need to update those k8s resources,
pulumi up
seemingly tries to re-create them instead of just `kubectl apply`ing over top (which would just update). Anyone else seen this or have a workaround?
b

billowy-army-68599

12/08/2021, 10:07 PM
can you clarify a bit more what workflow you're using?
w

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 :)
m

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. 🙂
w

wonderful-twilight-70958

12/09/2021, 2:01 PM
Are you using chart or release for 1?
I'm using Release and that use case works fine for me.
m

mammoth-airline-91759

12/10/2021, 5:34 AM
Remote Chart for 1
I saw the Release option, but didn’t choose it for some reason…