upgrade: add Longhorn CRD migrations during upgrade #9284
Conversation
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
4e1bef9 to
7d00949
Compare
innobead
requested changes
Oct 9, 2025
7d00949 to
069770a
Compare
475963c to
91f3a05
Compare
ibrokethecloud
previously approved these changes
Oct 12, 2025
innobead
requested changes
Oct 13, 2025
- we need to take care the dropped v1beta1 resource.
- This is the corner case only if user starts Harvester from v1.0,
Longhorn v1.2.4 (v1beta1)
Co-authored-by: David Ko <[email protected]>
Signed-off-by: Vicente Cheng <[email protected]>
d536ecd to
6ae6fa6
Compare
ibrokethecloud
approved these changes
Oct 23, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Problem:
Need to take care of the Longhorn v1beta1 resource
Solution:
Migrate/Cleanup the v1beta1 resource if needed
Related Issue(s):
#9269
Test plan:
Upgrade from v1.6.x and ensure everything is OK.
We need to ensure the common path is not affected
Additional documentation or context