Closed soujiro32167 closed 1 month ago
Thanks for reporting this issue @soujiro32167. I am able to reproduce this. Note that the same issue also exists for ConfigMaps if we set CMs to be mutable within our k8s provider setup. The issue doesn't exist for CMs in the repro, since our provider is doing a replacement, which goes through a different flow for saving state compared to an update flow.
The bug most likely is being triggered here: https://github.com/pulumi/pulumi-kubernetes/blob/41b0d90d1f9e1c552878671519e241b358615ece/provider/pkg/provider/provider.go#L2365
We should store newInputs
instead of oldLive
similar to what we do in the Create
flow (ref: https://github.com/pulumi/pulumi-kubernetes/blob/41b0d90d1f9e1c552878671519e241b358615ece/provider/pkg/provider/provider.go#L1865).
Thank you!
What happened?
Using a kubernetes provider with
renderYamlToDirectory
, I want to create a deployment and configmap.The resources get created successfully. After a second
pulumi up
, no changes are observed.However, after updating the deployment, the pulumi state will not update. Updating the configmap works fine
To reproduce:
pulumi up -s repro
containerPort: 9090
pulumi up -s repro --diff
shows the diff correctlyyes
to apply the changespulumi up -s repro --diff
shows the same diff, even though the change was already appliedNote: the yaml
yamls/apps_v1-deployment-myns-my-deployment.yaml
gets updated correctlyExample
Output of
pulumi about
Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction. To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).