update operator-sdk to 1.28.0 & apply all migrations #257
Conversation
This file contains 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
|
Looks good to me! I guess we'll perform the |
r65535
approved these changes
Apr 26, 2023
Yes i believe so. It's not clear to me at the moment how to migrate, but when we do move to go/v4 we will probably need to apply all of the v4 migrations |
juldrixx
approved these changes
Apr 28, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What's in this PR?
Update operator-sdk to 1.28.0 and apply all kubebuilder migrations specified here:
https://sdk.operatorframework.io/docs/upgrading-sdk-version/
I upgraded my local operator-sdk by following their installation instructions documented here: https://sdk.operatorframework.io/docs/installation/
Checklist