Deployments are being replaced unnecessarily #2262
Labels
kind/bug
Some behavior is incorrect or out of spec
last-applied-configuration
Issues related to the last-applied-configuration annotation
resolution/fixed
This issue was fixed
What happened?
I have recently noticed in a number of our recent Pulumi runs that K8S resources are being unnecessarily replaced instead of updated, but I do not understand what is triggering this behaviour.
Steps to reproduce
When running preview (this is using Automation API) where the only that has changed is the contents of a
Secret
I can see in the Pulumi web app:Note that the summary includes 2 resources to be replaced but does not output the 2nd one, the
Deployment
, only theSecret
.Looking at the
Diff
tab theDeployment
replacement is listed (almost all is highlighted in red up until spec.replicas when the diff view becomes green, before reverting to red for last status):Additionally, the
Secret
is listed, as below as a replacement. We have only updated a single value within the secret so would not expect a replacementExpected Behavior
Existing
Deployment
andSecret
is updatedActual Behavior
Deployment
andSecret
are replacedOutput 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).
The text was updated successfully, but these errors were encountered: