CI migration Plan for containerd v2.0

[pacoxu]

#33761
@dims switched some of the CI jobs to v2.0.

Are we losing coverage for these jobs by promoting to 2.0? ie we lose 1.7 tests and gain the 2.0?

#33761 (comment) as @kannon92 pointed out, we also may need to keep some tests on containerd v1.7.

I open this issue on the CI migration plan. Will we migrate in this release cycle(v1.33) or later?

• there are some containerd v2 support WIP PRs in other subprojects like kubespray [containerd] Support containerd v2.0.x kubernetes-sigs/kubespray#11845.

https://github.com/containerd/containerd/blob/main/RELEASES.md#kubernetes-support

Kubernetes Version	containerd Version	CRI Version
1.29	1.7.11+, 1.6.27+	v1
1.30	2.1.0+, 2.0.0+, 1.7.13+, 1.6.28+	v1
1.31	2.1.0+, 2.0.0+, 1.7.20+, 1.6.34+	v1
1.32	2.1.0+, 2.0.1+, 1.7.24+, 1.6.36+	v1
1.33	2.1.0+, 2.0.4+, 1.7.24+, 1.6.36+	v1

For COS, https://cloud.google.com/container-optimized-os/docs/release-notes

• Milestone 117 is still using containerd 1.7.
• Dev upgraded containerd to v2.0.0.

[kannon92]

I'll bring this up in our sig-node-ci meeting.

[BenTheElder]

FYI There's a pending PR in kind to switch to 2.0.1 as well. We only use one version there.

[SergeyKanzhelev]

/cc @chrishenzie

[BenTheElder]

We landed containerd 2.0.2 in kind. So ~all of those jobs are switched.

kubernetes-sigs/kind#3848
kubernetes-sigs/kind#3828

[BenTheElder]

/sig node

[pacoxu]

kubernetes/kubernetes#129818 may be caused by containerd 2.0 upgradation.(I am not sure about if the root cause is the upgradation.)

Do we find other failures after using containerd 2.0?

[HirazawaUi]

kubernetes/kubernetes#129818 may be caused by containerd 2.0 upgradation.(I am not sure about if the root cause is the upgradation.)

Do we find other failures after using containerd 2.0?

I've identified the root cause as the containerd upgrade. Ref: kubernetes/kubernetes#129818 (comment)

[chrishenzie]

/assign