-
Notifications
You must be signed in to change notification settings - Fork 684
feat: enforce Kubernetes version compatibility #11208
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
1153e7b
to
13f9d76
Compare
I removed the upgrade pre-checks for Kubernetes version, as now they are handled by the config validation anyways - config validation with new |
6db6614
to
8ed5e1f
Compare
8ed5e1f
to
cd83074
Compare
|
||
expectedVersion string | ||
}{ | ||
{ |
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.
maybe also have ones without tag and one with just sha and no tag
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 don't allow no tag, as we won't be able to guess the version this way....
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.
but this might be a breaking change, so I will add a note that the tag is required
Fixes siderolabs#11198 We should enforce in following places: * before starting `upgrade-k8s`, check that all Talos machines would end up with a valid version * validate in Talos machine configuration, this will cover both upgrades, new installs, and any machine configuration manual edits Signed-off-by: Andrey Smirnov <[email protected]>
cd83074
to
4da2dd5
Compare
/m |
Fixes #11198
We should enforce in following places:
upgrade-k8s
, check that all Talos machines would end up with a valid version