Skip to content

chore(deps): update dependency kubernetes-sigs/kind to v0.33.0 - #110

Open
scality-renovate[bot] wants to merge 1 commit into
mainfrom
renovate/kubernetes-sigs-kind-0.x
Open

chore(deps): update dependency kubernetes-sigs/kind to v0.33.0#110
scality-renovate[bot] wants to merge 1 commit into
mainfrom
renovate/kubernetes-sigs-kind-0.x

Conversation

@scality-renovate

@scality-renovate scality-renovate Bot commented Nov 9, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Update Change
kubernetes-sigs/kind minor v0.30.0 → v0.33.0

Release Notes

kubernetes-sigs/kind

v0.33.0

Compare Source

This release contains critical dependency updates, bug fixes, and defaults to Kubernetes 1.37.0.

Breaking Changes

The default node image is now kindest/node:v1.37.0@sha256:a1ed56cfb0e7b93589bdf97c8cd566405a265939e3620fc4f5de89adff580ae5.

New Features

  • Assorted dependency updates.

Images pre-built for this release:

  • v1.37.0: kindest/node:v1.37.0@sha256:a1ed56cfb0e7b93589bdf97c8cd566405a265939e3620fc4f5de89adff580ae5
  • v1.36.4: kindest/node:v1.36.4@sha256:099e049362a1526b2db71494e1947aae99bd16290d7c895f2b7ea312e3cbfaed
  • v1.35.8: kindest/node:v1.35.8@sha256:07b2536e30b803ed61d1677a79df6115f798ce64c80f9e22f6ed45afd09323c0
  • v1.34.11: kindest/node:v1.34.11@sha256:44e222ee2132dab25ff87301682f89eb82c7880ea3a1bf543bfe9708fd08d67d

NOTE: You must use the @sha256 digest to guarantee an image built for this release, until such a time as we switch to a different tagging scheme. Even then we will highly encourage digest pinning for security and reproducibility reasons.

See also:

NOTE: These node images support amd64 and arm64, both of our supported platforms. You must use the same platform as your host, for more context see #​2718

Fixes

  • Respect Docker client proxy config for docker nodes. (#​4192)
  • Preserve external load balancer CDS/LDS configuration across container restarts. (#​4195)
  • Improve local-path-provisioner helperPod tolerations. (#​4210)
  • Assorted documentation fixes and improvements.

Contributors

Committers for this release:

We'd also like to thank everyone who touched the codebase, filed issues, and helped the community!

v0.32.0

Compare Source

This release contains critical dependency updates, bug fixes, and defaults to Kubernetes 1.36.1.

Breaking Changes

  • The default node image is now kindest/node:v1.36.1@sha256:3489c7674813ba5d8b1a9977baea8a6e553784dab7b84759d1014dbd78f7ebd5
  • New node images requiring upgrading kind to kind load ...: Due to a containerd upgrade, you must upgrade kind to this release or newer to use kind load ... with the newly published node images. As always, we cannot gurantee full compatibility of node images between kind releases. You can use the digests from previous releases, upgrade kind, or build your own node-images.
  • kubeadm v1beta4 config format is now used for Kubernetes 1.36.0+ If you are using versioned config patches, you must update to target v1beta4. Unversioned patches kind will attempt to convert as needed (more below in New Features). This change is required for Kubernetes 1.37+ which drops kubeadm v1beta3 config.
  • Adoption of Envoy for Load Balancing in multi-control-plane node clusters: HAProxy has been replaced by Envoy (docker.io/envoyproxy/envoy:v1.36.2) as the load balancer in multi-control-plane (HA) clusters. If you rely on custom HAProxy loadbalancer configurations or images, please note that Envoy is now used.
  • cgroup v1 warning: A warning is now printed if cgroup v1 is detected on the host. Kubernetes has deprecated support for cgroup v1, and at some point in the future KIND releases / node-images will also drop support for cgroup v1.

New Features

  • kubeadm v1beta4 configuration support: KIND now uses the v1beta4 config format for Kubernetes v1.36.0+ while maintaining v1beta3 for v1.23.0 up to v1.35.x, and v1beta2 for older versions.
  • Custom Merging & Version-Awareness for Kubeadm Config Patches:
    • KIND now automatically translates old-style map-based extraArgs / kubeletExtraArgs patches to the list-based v1beta4 format when targeting v1beta4 configs.
    • Config patches now append to extraArgs / kubeletExtraArgs / certSANs reliably. To overwrite or make other more precise patching, use json6902 patches.
  • Support for containerd config v4 format: Enabled support for containerd's config v4 format in kind load and snapshotter parsing, which is required for newer containerd versions.
  • Building Node Images from CI Artifacts: Added support to build node images from Kubernetes CI artifacts (resolving endpoints like https://dl.k8s.io/ci/latest.txt or CI build prefixes).
  • Support for containerd version-aware containerd config patching: Like kubeadmConfigPatches, containerd config patching is now aware of version and if specified in patches will only apply patches that match the containerd config being used.
  • Assorted dependency updates.

Images pre-built for this release:

  • v1.36.1: kindest/node:v1.36.1@sha256:3489c7674813ba5d8b1a9977baea8a6e553784dab7b84759d1014dbd78f7ebd5
  • v1.35.5: kindest/node:v1.35.5@sha256:ce977ae6d65918d0b58a5f8b5e940429c2ce42fa3a5619ec2bbc60b949c0ac95
  • v1.34.8: kindest/node:v1.34.8@sha256:02722c2dedddcfc00febf5d27fbeb9b7b2c14294c82109ff4a85d89ac9ba3256
  • v1.33.12: kindest/node:v1.33.12@sha256:3f5c8443c620245e4d355cfe09e96a91ead32ceaa569d3f1ca9edf0cb2fe2ff4

NOTE: You must use the @sha256 digest to guarantee an image built for this release, until such a time as we switch to a different tagging scheme. Even then we will highly encourage digest pinning for security and reproducibility reasons.

Fixes

  • Fix permission error when creating pods with hostUsers: false (Kubernetes 1.36+).
  • Handle registry ports correctly in image normalization logic (e.g., registry running on ports like localhost:5000/...).
  • Handle empty port mapping listen addresses correctly (defaults to wildcard address).
  • Skip /dev/mapper mount on rootless Docker.
  • Assorted documentation fixes and improvements.

See also:

NOTE: These node images support amd64 and arm64, both of our supported platforms. You must use the same platform as your host, for more context see #​2718

Contributors

Committers for this release:

We'd also like to thank everyone who touched the codebase, filed issues, and helped the community!

v0.31.0

Compare Source

This release contains dependency updates and defaults to Kubernetes 1.35.0.

Please take note of the breaking changes from Kubernetes 1.35, and how to prepare for future changes to move off of the deprecated kubeam v1beta3 in favor of v1beta4. We will include updated reminders for both again in subsequent releases.

Breaking Changes

The default node image is now kindest/node:v1.35.0@sha256:452d707d4862f52530247495d180205e029056831160e22870e37e3f6c1ac31f

Kubernetes 1.35+ Cgroup v1

Kubernetes will be removing cgroup v1 support, and therefore kind node images at those versions will also be dropping support.

You can read more about this change in the Kubernetes release blog: https://kubernetes.io/blog/2025/12/17/kubernetes-v1-35-release/#removal-of-cgroup-v1-support

If you must use kind on cgroup v1, we recommend using an older Kubernetes release for the immediate future, but we also strongly recommend migrating to cgroup v2.

In the near future as Kubernetes support dwindles, KIND will also clean up cgroup v1 workarounds and drop support in future kind releases and images, regardless of Kubernetes version.

Most stable linux distros should be on cgroupv2 out of the box.

This is a reminder to use pinned images by digest, see the note below about images for this release.

Kubeadm Config *Future* Breaking Change

WARNING: Future kind releases will adopt kubeadm v1beta4 configuration, kubeadm v1beta4 has a breaking change to extraArgs: https://kubernetes.io/blog/2024/08/23/kubernetes-1-31-kubeadm-v1beta4/.

If you use the kubeadmConfigPatches feature then you may need to prepare for this change.
We recommend that you use versioned config patches that explicitly match the version required.

KIND uses kubeadm v1beta3 for Kubernetes 1.23+, and will likely use v1beta4 for Kubernetes 1.36+
The exact version is TBD pending work to fix this but expected to be 1.36.
It will definitely be an as-of-yet-unreleased Kubernetes version to avoid surprises, and it will not be on a patch-release boundary.

KIND may still work with older Kubernetes versions at v1beta2, but we no longer test or actively support these as Kubernetes only supports 1.32+ currently: https://kubernetes.io/releases/

You likely only need v1beta3 + v1beta4 patches, you can take your existing patches that work with v1beta3, explicitly set apiVersion: kubeadm.k8s.io/v1beta3 in the patch at the top level, and make another copy for v1beta4. The v1beta4 patch will need to move extraArgs from a map to a list, for examples see: https://kubernetes.io/docs/reference/config-api/kubeadm-config.v1beta4/

For a concrete example of kind config with kubeadm config patch targeting both v1beta3 and v1beta4, consider this simple kind config that sets verbosity of the apiserver logs:

kind: Cluster
apiVersion: kind.x-k8s.io/v1alpha4
kubeadmConfigPatches:

# patch for v1beta3 (1.23 ...)
- |
  kind: ClusterConfiguration
  apiVersion: kubeadm.k8s.io/v1beta3
  apiServer:
    extraArgs:
      "v": "4"

# patch for v1beta4 (future)
- |
  kind: ClusterConfiguration
  apiVersion: kubeadm.k8s.io/v1beta4
  apiServer:
    extraArgs:
      - name: "v"
        value: "4"

If you only need to target a particular release, you can use one version.

If you only need to target fields that did not change between kubeadm beta versions, you can use a versionless patch, which may be more convenient, but we cannot guarantee there will be no future kubeadm config breaking changes.

New Features

  • Assorted unspecified dependency updates

Images pre-built for this release:

  • v1.35.0: kindest/node:v1.35.0@sha256:452d707d4862f52530247495d180205e029056831160e22870e37e3f6c1ac31f
  • v1.34.3: kindest/node:v1.34.3@sha256:08497ee19eace7b4b5348db5c6a1591d7752b164530a36f855cb0f2bdcbadd48
  • v1.33.7: kindest/node:v1.33.7@sha256:d26ef333bdb2cbe9862a0f7c3803ecc7b4303d8cea8e814b481b09949d353040
  • v1.32.11: kindest/node:v1.32.11@sha256:5fc52d52a7b9574015299724bd68f183702956aa4a2116ae75a63cb574b35af8
  • v1.31.14: kindest/node:v1.31.14@sha256:6f86cf509dbb42767b6e79debc3f2c32e4ee01386f0489b3b2be24b0a55aac2b

NOTE: You must use the @sha256 digest to guarantee an image built for this release, until such a time as we switch to a different tagging scheme. Even then we will highly encourage digest pinning for security and reproducibility reasons.

See also:

NOTE: These node images support amd64 and arm64, both of our supported platforms. You must use the same platform as your host, for more context see #​2718

Fixes

  • Detect additional edge case with ipv6 support on the host
  • Make development / release scripts GOTOOLCHAIN aware

Contributors

Committers for this release:

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • "before 9am on monday"
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate CLI.

@scality-renovate
scality-renovate Bot requested a review from a team as a code owner November 9, 2026 03:16
@scality-renovate scality-renovate Bot added dependencies Pull requests that update a dependency file minor labels Nov 9, 2026
@github-actions

github-actions Bot commented Nov 9, 2026

Copy link
Copy Markdown

Dependency Bump Evaluation

Version change: kubernetes-sigs/kind v0.30.0 -> v0.33.0 (CI tool only, .github/workflows/test-e2e.yml)
Semver bump type: minor (pre-1.0, three releases jumped)

Changes:

  • Default node image moves from Kubernetes 1.34 to 1.37.0 (v0.31: 1.35, v0.32: 1.36.1, v0.33: 1.37.0)
  • v0.32: kubeadm v1beta4 config used for K8s 1.36+, HAProxy replaced by Envoy for multi-control-plane LB, containerd config v4 support, kind load requires kind >= v0.32 with the new node images
  • v0.33: Docker client proxy config respected, LB config preserved across restarts, local-path-provisioner toleration tweaks
  • cgroup v1 deprecation warnings (K8s 1.35+ drops cgroup v1)

Breaking changes: Yes upstream, but none appear to affect this repo:

  • kubeadmConfigPatches / v1beta4 extraArgs change: not used. The Makefile runs a plain kind create cluster --name $(KIND_CLUSTER) with no config file.
  • Envoy LB: only applies to HA clusters. The e2e cluster is a single node.
  • kind load compatibility: test/utils/utils.go uses kind load docker-image. Upgrading kind together with the default node image is the supported combination.
  • cgroup v1: the runner is ubuntu-26.04, which uses cgroup v2.

Security concerns: None. Upstream calls these "critical dependency updates" (Go/containerd) for a test-only binary. kind is still downloaded by tag without checksum verification, which is unchanged by this PR.

Impact on codebase: Only the e2e test cluster is affected. The default cluster now runs Kubernetes 1.37, which matches k8s.io/client-go/api v0.37.1 and the envtest version derived from k8s.io/api in go.mod. That is better alignment than today (kind v0.30 runs 1.34). Cert-manager and Prometheus operator manifests installed during e2e should be checked against 1.37 by the e2e run.

Recommendation: REVIEW REQUIRED

Notes: This looks low risk. It is not approved yet for two reasons: (1) CI is still running, including test-e2e / Run on Ubuntu, which is the only job that exercises this change; (2) the PR is authored by scality-renovate[bot], and the policy only allows auto-approval of dependabot PRs. Merge once test-e2e is green. .devcontainer/post-install.sh installs kind latest, so local dev environments are already on this version line.

— Claude Code

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@g-carre g-carre Awaiting requested review from g-carre g-carre is a code owner automatically assigned from scality/platform-dev
@ezekiel-alexrod ezekiel-alexrod Awaiting requested review from ezekiel-alexrod ezekiel-alexrod is a code owner automatically assigned from scality/platform-dev

At least 1 approving review is required to merge this pull request.

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file minor

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants