WIP: Add startup code to apiserver to migrate etcd keys #7567
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.
@erictune mentioned in #3476 that, as part of the work adding a custom etcd prefix, we should also add a flag to tell the apiserver what old, possibly empty prefix, to copy old data from. In the apiserver startup code the etcd keys should be migrated those flags.
I played around with some migration code and thought I would share it with you in a WIP branch to see if this is the general way it should go.
Would be grateful for any comments.
Refs: #3476