bump containerd and cri-tools to latest

[MaXinjian]

Signed-off-by: Ma Xinjian maxj.fnst@fujitsu.com

[k8s-ci-robot]

Hi @MaXinjian. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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/test-infra repository.

[BenTheElder]

is there any particular change noteworthy in these tools?

[MaXinjian]

is there any particular change noteworthy in these tools?

cri-tools #724 is meaningful

[aojea]

/ok-to-test
it is my bugfix for the port forwarding
containerd/containerd@1b05b60

[MaXinjian]

/retest

[MaXinjian]

ping

[tao12345666333]

/lgtm

[aojea]

final 1.5.0 was released 3 days ago
https://github.com/containerd/containerd/releases/tag/v1.5.0

[aojea]

/lgtm

@BenTheElder do we want to handle this bump independently or should we wait for the release?

[MaXinjian]

/test pull-kind-e2e-kubernetes-1-20

[BenTheElder]

@BenTheElder do we want to handle this bump independently or should we wait for the release?

I would like us to bump to 1.5.0 for the release
you can also do these antonio, just keep an eye on CI afterwards and maybe test it locally, sometimes it does regress for our usage.

[BenTheElder]

working on the image(s) for this.

[BenTheElder]

for reference @aojea:

1. check out the PR. I use an alias in my dotfiles github-checkout-upstream-pr https://github.com/BenTheElder/dotfiles/blob/abb07d8614a96617d35de7597ec5e7b4ac502c16/.bashrc.common.inc#L42
2. fetch upstream
3. rebase upstream/main so we are pushing from latest
4. make -C images/base push
5. commit upgrading the default image
6. push to the PR branch, instructions on github

[BenTheElder]

sorry i've been semi-unavailable myself. mostly had time for a few breaking bugs and otherwise been ~out.

[BenTheElder]

/approve

[BenTheElder]

/hold
kubernetes/kubernetes#101989

we should investigate if this bumps us to runc rc93 or not, rc93 has serious performance regression with kubelet apparently that is fixed in rc94 which is still be rolled out to projects like containerd

[BenTheElder]

containerd/containerd@de6db40 seems to only be at HEAD containerd/containerd#5473 and containerd 1.5.0 was definitely released with rc93, not sure if it was at rc93 in the version we already have.

[aojea]

👍

[BenTheElder]

containerd/containerd@v1.5.0...master looks like we should just bump to HEAD instead of sticking to the nice tagged release. current head is not far ahead, looks like mostly bug fixes.

[dims]

containerd 1.5.1 will roll out in a day or so @BenTheElder @aojea

[BenTheElder]

containerd 1.5.1 will roll out in a day or so @BenTheElder @aojea

thanks that's good to know.
we've shipped untagged versions before to pick up fixes and we're pretty badly in need of a release.
we should probably not ship rc93 just to get a tag.

[BenTheElder]

kind-ci/containerd-nightlies@fe50612 the nightly build needed to cover the 1.5 branch, updated that and kicked off an earlier build so we can pick it up (scheduled builds are nightly)

[BenTheElder]

1.5.0-17-g799eef87c is now available, HEAD of release/1.5 branch.

[dims]

@BenTheElder 1.5.1 is out and it uses runc rc94 !!

[BenTheElder]

/lgtm
/approve
/hold cancel

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: BenTheElder, MaXinjian

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:

• OWNERS [BenTheElder]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment