What happened:

When creating a cluster using kind v0.3.0 the resulting nodes contain an unexpected containerd version - v2.1.3.

What you expected to happen:

containerd version in node is v2.1.4 as documented in the kind v0.3.0 release notes. containerd v2.1.4 addresses multiple issues, including one that impacts the ability of a node to pull images at all (containerd/containerd#12127).

How to reproduce it (as minimally and precisely as possible):

Create a cluster with kind v0.3.0. This affects all clusters equally.

Anything else we need to know?:

Some digging showed me that the base image used by kind to build node images has not been updated with the v0.3.0 release. This includes both the image itself, which has not been updated, as well as the reference to the image (pkg/build/nodeimage/defaults.go).

When building the base image using the tooling in the repository one ends up with an image that comes with containerd v2.1.4, but still contains v0.29.0 in the image tag. This in turn seems to be caused by v0.3.0 being a lightweight git tag and not an annotated git tag.

Environment:

• kind version: (use kind version): kind v0.30.0 go1.25.0 darwin/arm64