Add support for --migrating-field-managers#540
Closed
jveski wants to merge 5 commits into
Closed
Conversation
Collaborator
|
Thanks Jordan, I have reproduced the issue locally and will try apply this PR to see if it would fix the issue. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Allows users to specify one or more SSE field managers that Eno should take ownership from before making any changes to a resource.
This is useful for migration scenarios where a field is removed from an object during Eno's first update (to that object). Without first taking ownership of the previous manager's fields, apiserver will just ignore the empty field sent by Eno instead of pruning it.