-
Notifications
You must be signed in to change notification settings - Fork 240
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
[release/v1.4] Updates to kubernetes-cni, cri-tools, and supported Kubernetes versions #2628
Conversation
Signed-off-by: Marko Mudrinić <mudrinic.mare@gmail.com>
Signed-off-by: Marko Mudrinić <mudrinic.mare@gmail.com>
Signed-off-by: Marko Mudrinić <mudrinic.mare@gmail.com>
Signed-off-by: Marko Mudrinić <mudrinic.mare@gmail.com>
Signed-off-by: Marko Mudrinić <mudrinic.mare@gmail.com>
Signed-off-by: Marko Mudrinić <mudrinic.mare@gmail.com>
Skipping CI for Draft Pull Request. |
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.
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ahmedwaleedmalik The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
LGTM label has been added. Git tree hash: 26ebec9df60a23596cbb5c392fa5c907f7c34cba
|
We'll tackle this in another PR. |
What this PR does / why we need it:
The latest (January 2023) Kubernetes patch releases introduced some changes to packages that are described in #2607.
We were able to easily mitigate issues on main and
release/v1.5
because those branches/versions are using containerd 1.6.However, we cannot do that easily for
release/v1.4
because it's using containerd 1.5 and cri-tools v1.26.0 doesn't support containerd 1.5. Updating containerd to 1.6 at this point would be too complicated because we have to update it in machine-controller, OSM, and KubeOne itself.The idea for this PR is:
--force
flagWhat type of PR is this?
/kind bug
/kind api-change
Does this PR introduce a user-facing change? Then add your Release Note here:
Documentation: