Skip to content
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

Backported patch updates not rolled on newer releases? #11555

Closed
blackluck opened this issue Sep 19, 2024 · 5 comments
Closed

Backported patch updates not rolled on newer releases? #11555

blackluck opened this issue Sep 19, 2024 · 5 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@blackluck
Copy link

What would you like to be added

Maybe if component patches backported to older versions then create for new releases too.
Or create policy to not release new kubespray patch in older versions until newer kubespray minor releases also updated with it.
Or something to not forget patches from other version missed in newer minor versions.

Why is this needed

Kubespray release 2.24 got lot of new component patch version updates to a newer version in 2.24.3 (released 2 days ago) #11516 :
Default to kubernetes v1.28.14
Default to etcd v3.5.16
Default to containerd v1.7.22
Default to cri-o v1.28.10
Default to nerdctl 1.7.7
Default to runc v1.1.14

It's one thing could not see why these patch updates needed for 2.24, but why there is no 2.25.1, 2.26.1 releases with at least these component versions?

2.25 still only hase 2.25.0 version (released may 21) and also 2.26 only initial 2.26.0 patch version (released 2 weeks ago). Both of them have OLDER version in some of those components (etcd, containerd, nerdctl, runc).
Which means after I updated with 2.24 release and going to update to 2.25, those components will be DOWNGRADED and even after updating to 2.26 those components will be older then installed with 2.24.
I know downgrade only in patch versions but for pretty important components like etcd, containerd, runc.
And if those don't have problems with older patch version why needed to update them in 2.24?

@blackluck blackluck added the kind/feature Categorizes issue or PR as related to a new feature. label Sep 19, 2024
@tico88612
Copy link
Member

@VannTen Maybe we need to check before the next release to see if there's a possibility of the kit version being downgraded?

@VannTen
Copy link
Contributor

VannTen commented Sep 20, 2024 via email

@janosbabik
Copy link
Contributor

Hi @VannTen, are there any plans to bump the versions of these components (etcd, runc, containerd...) in the 2.25 and 2.26 branches as well?
I would like to update from 2.24.3 -> 2.25.0 -> 2.26.0, and I'm curious whether downgrading these apps could cause any problems.

@VannTen
Copy link
Contributor

VannTen commented Sep 25, 2024 via email

@VannTen
Copy link
Contributor

VannTen commented Oct 4, 2024

Closing this as I think this has been answered

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

No branches or pull requests

4 participants