-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
upgrade: do not apply 2.7 migration for patch-upgrades #1649
Conversation
✅ Deploy Preview for constellation-docs canceled.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Check looks correct.
25a860c
to
5d31252
Compare
5d31252
to
f1f93d9
Compare
Azure, 1+1, 2.7 -> 2.7.1, k8s-only 🟢 Testing 2.6.0 -> 2.7.1 upgrade manually by running: Separate invocation for microservice upgrade: Reason for testing this manually: |
3909975
to
aec6a49
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Azure, 1+1, 2.7.0 -> 2.7.1, microservice only 🟢 Manual test based on 2.6.0 worked: |
Also correctly set microservice version from config. Previously the key was ignored and microservices were always tried for an upgrade.
This allows us to build a CLI that reports the given version during an upgrade test. With this we can test patch upgrades.
pre-release versions and release versions behaved differently. This lead to a duplicate v prefix in the cli's version.
c4c165e
to
f41281a
Compare
* upgrade: fix 2.6 -> 2.7 migration for 2.7.1 patch Also correctly set microservice version from config. Previously the key was ignored and microservices were always tried for an upgrade. * ci: add simulatedTargetVersion to e2e-upgrade This allows us to build a CLI that reports the given version during an upgrade test. With this we can test patch upgrades. Signed-off-by: Otto Bittner <[email protected]> * ci: e2e-upgrade, case-insensitive string compare * hack: fix v-prefixing in pseudo-version tool pre-release versions and release versions behaved differently. This lead to a duplicate v prefix in the cli's version. Signed-off-by: Otto Bittner <[email protected]> --------- Signed-off-by: Otto Bittner <[email protected]> Co-authored-by: Otto Bittner <[email protected]>
Proposed change(s)
ID key digest policy MAAFallback is not supported for upgrades
on clusters that are created with CLI versionv2.7
.Checklist