Migrate persistent storage from previous MO versions #355
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.
Automatically migrate the persistent storage of MO on the controller if it originates from a previous MO version.
The persistent storage is extended and optimized in some new releases of MO, making the storage layout backwards-incompatible. To allow existing deployments to be continuously updated, it's necessary to handle the storage changes. The built-in migration is guaranteed to work from v1.2.0 onward. There could be some storage artifacts from before v1.2.0 which are not fully handled.
Examples includes: