Skip to content

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

Merged
merged 1 commit into from
Jun 27, 2025

Conversation

smira
Copy link
Member

@smira smira commented Jun 12, 2025

Fixes #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

@smira smira added this to the v1.11 milestone Jun 12, 2025
@smira smira marked this pull request as draft June 12, 2025 16:51
@smira smira force-pushed the feat/k8s-version-compat branch from 1153e7b to 13f9d76 Compare June 13, 2025 15:02
@smira smira marked this pull request as ready for review June 13, 2025 15:02
@smira
Copy link
Member Author

smira commented Jun 13, 2025

I removed the upgrade pre-checks for Kubernetes version, as now they are handled by the config validation anyways - config validation with new installer will ensure that Kubernetes version used in the cluster will match new Talos version

@smira smira force-pushed the feat/k8s-version-compat branch 2 times, most recently from 6db6614 to 8ed5e1f Compare June 13, 2025 16:08
@smira smira force-pushed the feat/k8s-version-compat branch from 8ed5e1f to cd83074 Compare June 27, 2025 09:50

expectedVersion string
}{
{
Copy link
Member

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

Copy link
Member Author

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....

Copy link
Member Author

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]>
@smira smira force-pushed the feat/k8s-version-compat branch from cd83074 to 4da2dd5 Compare June 27, 2025 16:03
@smira
Copy link
Member Author

smira commented Jun 27, 2025

/m

@talos-bot talos-bot merged commit 4da2dd5 into siderolabs:main Jun 27, 2025
55 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

talosctl Should not create an impossible situation to recover from (upgrade k8s past os supported version)
4 participants