-
Notifications
You must be signed in to change notification settings - Fork 88
Update compatibility list #726
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
Conversation
Signed-off-by: Andres Taylor <[email protected]>
timvaillancourt
left a comment
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, caveat: I don't know if a newer Kube version could be used
Signed-off-by: Matt Lord <[email protected]>
Signed-off-by: Matt Lord <[email protected]>
Signed-off-by: Matt Lord <[email protected]>
Signed-off-by: Matt Lord <[email protected]>
Signed-off-by: Matt Lord <[email protected]>
Signed-off-by: Matt Lord <[email protected]>
Signed-off-by: Matt Lord <[email protected]>
Signed-off-by: Matt Lord <[email protected]>
Signed-off-by: Matt Lord <[email protected]>
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.
We just need to make two small changes once we have an actual v23.0.0 release to use in the tests:
- Change all of these
22.0.1image versions to23.0.0[-rc1](or whatever the tag ends up being) so that the upgrade test is testing GA->latest (v23->v24) again: https://github.com/search?q=repo%3Aplanetscale%2Fvitess-operator%2022.0.1&type=code - Then since it's all v23 and later we can convert the last remaining instance of the
tablet_refresh_intervalflag totablet-refresh-interval:tablet_refresh_interval: 10s
So then 101_initial_cluster.yaml (the main place where we'll be replacing 22.0.1 with 23.0.0) starts up a v23 cluster and then upgrades to v24 in the upgrade test (right now it's v22->v24 as we have no v23 release images yet).
Signed-off-by: Matt Lord <[email protected]>
No description provided.