-
Notifications
You must be signed in to change notification settings - Fork 1.7k
upgrade containerd, fuse overlayfs, go #3978
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
|
should be safe ™️ |
|
/lgtm Go ahead with unfreeze when comfortable. ;) |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: BenTheElder, stmcginnis 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 |
|
I guess let's roll this in a few PRs since there's no rush, we can let the automated build push the base image next mostly just picking up some "easy" "safe" updates ahead of our next release (at the very least I want to align one to k8s 1.34) /hold cancel thanks! |
|
@BenTheElder: The following tests failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
|
those are expected, we're going to have to patch the CI and/or drop them, it is kubernetes/kubernetes#133261 |
|
will look at the 1.28..1.29 CI in a bit |
|
wednesday is also the 1.34 branch cut, it would be a good time to rotate the CI jobs and make sure we stand up the 1.34 jobs for this repo |
|
the postsubmit didn't run? https://prow.k8s.io/?repo=kubernetes-sigs%2Fkind&type=postsubmit |
|
I'm having issues with containerd version 2.1.1 having segfaults, I'm seeing this in kube-network-policies CI that createas a bunch of pods with multiple containers inside very quickly
If I build containerd from latest in the 2.1 release and 2.1.4 does not have the problem, I need to confirm if is still one containerd versions |
No description provided.