Field manager name conflicts for resources created with client-side apply #2352
Labels
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
Milestone
What happened?
Recent versions of kubernetes began setting a field manager for all resources based on the name of the executable performing the update, even for resources managed using client-side apply. This can cause problems for resources that were created using client-side apply that are subsequently updated using server-side apply because the field manager name may conflict.
Related: #2262
Expected Behavior
Updating a resource created using client-side apply mode should not cause conflicts based on the field manager name.
Steps to reproduce
Example:
Results in the following error:
Output of
pulumi about
n/a
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: