DaemonSetPatch
taking ownership of fields unexpectedly upon an update operation with a parent set.
#2718
Labels
customer/feedback
Feedback from customers
customer/lighthouse
Lighthouse customer bugs and enhancements
kind/bug
Some behavior is incorrect or out of spec
p1
A bug severe enough to be the next item assigned to an engineer
resolution/fixed
This issue was fixed
What happened?
When attempting to update an DaemonSetPatch resource while a parent component is set, the DaemonSetPatch took ownership of all field previously owned by
kubectl-client-side-apply
. This leads to a broken state that requires manual intervention to repair.Example
Notes
If you create the resource, then change a field like the
image
to trigger an update, the behavior will occur.Code Example
Output of
pulumi about
Additional context
I will attach the resulting config and manager files once I get a fresh example stood up.
Related to #2692
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: