Change:
uses containerd for worker nodes by default, and latest release of uses by default base-image with containerd 1.6 for worker node. Unfortunately, CDI was merged into containerd 1.7, and CI at the moment uses binary from unreleased build 0.20-alpha. So running e2e tests locally for is failing unless when building node image a parameter is used with base-image that has 1.7 containerd. The need needs to be mentioned in DRA e2e Dynamic Resource Allocation e2e work locally when running them according to the instruction. Run DRA e2e with kind 0.19. The fix is coming shortly. 27, 1.28-alpha N/A N/A N/A N/A N/A
/sig node /assign
/triage accepted
I recommend testing kubernetes @ HEAD with KIND @ HEAD more generally. Nearly all of Kubernetes CI does this, we can't guarantee that a previously released binary has fixes to handle unreleased kubernetes breaking changes so periodically this is required regardless of this specific issue.
Alright, that recommendation was not noticed by me unfortunately. And thinking that there might be more like me, let's at least document it in the DRA e2e tests README.

Discussion:
in case that it needs that for operations like error injection or checking calls. <del> ## Cluster setup </del> <ins> ## Cluster setup preparation </ins> <del> The container runtime must support CDI. The latest cri-o releases contain support, containerd 1.6.x does not. To bring up a kind cluster with containerd built from their main branch, use: </del> <ins> The container runtime must support CDI. CRI-O supports CDI starting from release 1.23, Containerd supports CDI starting from release 1.7. To bring up a Kind cluster with Containerd, two things are needed: - [build binaries from Kubernetes source code tree](https://github.com/kubernetes/community/blob/master/contributors/devel/development.md#building-kubernetes) - [Kind](https://github.com/kubernetes-sigs/kind) </ins> <del> - [Bash version requirement](https://github.com/kubernetes/community/blob/master/contributors/devel/development.md#bash-version-requirement) </del> <ins> > NB: Kind switched to use worker-node base image with Containerd 1.7 by default starting from release 0.20, build kind from latest main branch sources or use Kind release binary 0.20 or later. </ins> <del> - Build node image </del> <ins> ### Build kind node image After building Kubernetes, in Kubernetes source code tree biuld new node image: </ins> ```bash <del> $ test/e2e/dra/kind-build-image.sh dra/node:latest </del> <ins> $ kind build node-image --image dra/node:latest $(pwd) </ins> ``` <del> - Bring up a kind cluster </del> <ins> ## Bring up a Kind cluster </ins> ```bash $ kind create cluster --config test/e2e/dra/kind.yaml --image dra/node:latest ```

<del> #!/usr/bin/env bash # Copyright 2022 The Kubernetes Authors. # # Licensed under the Apache License, Version 2.0 (the "License"); # you may not use this file except in compliance with the License. # You may obtain a copy of the License at # #     http://www.apache.org/licenses/LICENSE-2.0 # # Unless required by applicable law or agreed to in writing, software # distributed under the License is distributed on an "AS IS" BASIS, # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. # See the License for the specific language governing permissions and # limitations under the License. # This scripts invokes `kind build image` so that the resulting # image has a containerd with CDI support. # # Usage: kind-build-image.sh <tag of generated image> set -ex set -o pipefail # TODO (betheelder,pohly): this script is a bit of a no-op now, but people may # still be referencing it (CI is not). Clean up later. tag="$1" kind build node-image --image "$tag" "$(pwd)" </del>