chore(deps): update dependency kind to v0.33.0 - #44
Open
renovate[bot] wants to merge 1 commit into
Open
Conversation
renovate
Bot
force-pushed
the
renovate/kind-0.x
branch
from
September 19, 2025 16:09
2566cdb to
1fe8668
Compare
renovate
Bot
force-pushed
the
renovate/kind-0.x
branch
from
October 24, 2025 05:13
1fe8668 to
d05cf3d
Compare
renovate
Bot
force-pushed
the
renovate/kind-0.x
branch
from
November 12, 2025 11:01
d05cf3d to
7c7a424
Compare
renovate
Bot
force-pushed
the
renovate/kind-0.x
branch
from
December 10, 2025 03:03
7c7a424 to
f5f2402
Compare
renovate
Bot
force-pushed
the
renovate/kind-0.x
branch
from
December 17, 2025 20:12
f5f2402 to
a9271dc
Compare
renovate
Bot
force-pushed
the
renovate/kind-0.x
branch
from
December 18, 2025 03:37
a9271dc to
a83a557
Compare
renovate
Bot
force-pushed
the
renovate/kind-0.x
branch
from
January 21, 2026 13:57
a83a557 to
8b7ee8e
Compare
renovate
Bot
force-pushed
the
renovate/kind-0.x
branch
from
February 2, 2026 18:37
8b7ee8e to
e34a06a
Compare
renovate
Bot
force-pushed
the
renovate/kind-0.x
branch
from
February 10, 2026 20:34
e34a06a to
7fab5cc
Compare
renovate
Bot
force-pushed
the
renovate/kind-0.x
branch
from
February 27, 2026 02:42
7fab5cc to
22bf103
Compare
renovate
Bot
force-pushed
the
renovate/kind-0.x
branch
from
March 19, 2026 05:15
22bf103 to
bb79ba7
Compare
renovate
Bot
force-pushed
the
renovate/kind-0.x
branch
3 times, most recently
from
April 23, 2026 10:10
05a688a to
979c7d1
Compare
renovate
Bot
force-pushed
the
renovate/kind-0.x
branch
from
April 29, 2026 19:26
979c7d1 to
152157f
Compare
renovate
Bot
force-pushed
the
renovate/kind-0.x
branch
from
May 12, 2026 17:54
152157f to
a4f09d7
Compare
renovate
Bot
force-pushed
the
renovate/kind-0.x
branch
from
June 2, 2026 22:28
a4f09d7 to
deb4296
Compare
renovate
Bot
force-pushed
the
renovate/kind-0.x
branch
from
June 13, 2026 16:11
deb4296 to
7500c59
Compare
renovate
Bot
force-pushed
the
renovate/kind-0.x
branch
2 times, most recently
from
July 23, 2026 02:43
938b76f to
4de0c25
Compare
renovate
Bot
force-pushed
the
renovate/kind-0.x
branch
from
July 24, 2026 19:50
4de0c25 to
f771e58
Compare
renovate
Bot
force-pushed
the
renovate/kind-0.x
branch
from
August 11, 2026 21:37
f771e58 to
8d0229b
Compare
renovate
Bot
force-pushed
the
renovate/kind-0.x
branch
2 times, most recently
from
August 20, 2026 12:30
5670e8c to
d93945e
Compare
renovate
Bot
force-pushed
the
renovate/kind-0.x
branch
2 times, most recently
from
August 27, 2026 01:57
f60d907 to
823fb41
Compare
renovate
Bot
force-pushed
the
renovate/kind-0.x
branch
from
August 28, 2026 12:11
823fb41 to
22ff8bf
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
0.29.0→0.33.0Release Notes
kubernetes-sigs/kind (kind)
v0.33.0Compare 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.37.0@sha256:a1ed56cfb0e7b93589bdf97c8cd566405a265939e3620fc4f5de89adff580ae5.New Features
Images pre-built for this release:
kindest/node:v1.37.0@sha256:a1ed56cfb0e7b93589bdf97c8cd566405a265939e3620fc4f5de89adff580ae5kindest/node:v1.36.4@sha256:099e049362a1526b2db71494e1947aae99bd16290d7c895f2b7ea312e3cbfaedkindest/node:v1.35.8@sha256:07b2536e30b803ed61d1677a79df6115f798ce64c80f9e22f6ed45afd09323c0kindest/node:v1.34.11@sha256:44e222ee2132dab25ff87301682f89eb82c7880ea3a1bf543bfe9708fd08d67dNOTE: You must use the
@sha256digest 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
Contributors
Committers for this release:
We'd also like to thank everyone who touched the codebase, filed issues, and helped the community!
v0.32.0Compare Source
This release contains critical dependency updates, bug fixes, and defaults to Kubernetes 1.36.1.
Breaking Changes
kindest/node:v1.36.1@sha256:3489c7674813ba5d8b1a9977baea8a6e553784dab7b84759d1014dbd78f7ebd5kind load ...: Due to a containerd upgrade, you must upgradekindto this release or newer to usekind 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.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.New Features
v1beta4config format for Kubernetesv1.36.0+while maintainingv1beta3forv1.23.0up tov1.35.x, andv1beta2for older versions.extraArgs/kubeletExtraArgspatches to the list-basedv1beta4format when targetingv1beta4configs.extraArgs/kubeletExtraArgs/certSANsreliably. To overwrite or make other more precise patching, use json6902 patches.kind loadand snapshotter parsing, which is required for newer containerd versions.https://dl.k8s.io/ci/latest.txtor CI build prefixes).versionand if specified in patches will only apply patches that match the containerd config being used.Images pre-built for this release:
kindest/node:v1.36.1@sha256:3489c7674813ba5d8b1a9977baea8a6e553784dab7b84759d1014dbd78f7ebd5kindest/node:v1.35.5@sha256:ce977ae6d65918d0b58a5f8b5e940429c2ce42fa3a5619ec2bbc60b949c0ac95kindest/node:v1.34.8@sha256:02722c2dedddcfc00febf5d27fbeb9b7b2c14294c82109ff4a85d89ac9ba3256kindest/node:v1.33.12@sha256:3f5c8443c620245e4d355cfe09e96a91ead32ceaa569d3f1ca9edf0cb2fe2ff4NOTE: You must use the
@sha256digest 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
hostUsers: false(Kubernetes 1.36+).localhost:5000/...)./dev/mappermount on rootless Docker.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.0Compare 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:452d707d4862f52530247495d180205e029056831160e22870e37e3f6c1ac31fKubernetes 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
kubeadmConfigPatchesfeature 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/v1beta3in the patch at the top level, and make another copy for v1beta4. The v1beta4 patch will need to moveextraArgsfrom 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:
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
Images pre-built for this release:
kindest/node:v1.35.0@sha256:452d707d4862f52530247495d180205e029056831160e22870e37e3f6c1ac31fkindest/node:v1.34.3@sha256:08497ee19eace7b4b5348db5c6a1591d7752b164530a36f855cb0f2bdcbadd48kindest/node:v1.33.7@sha256:d26ef333bdb2cbe9862a0f7c3803ecc7b4303d8cea8e814b481b09949d353040kindest/node:v1.32.11@sha256:5fc52d52a7b9574015299724bd68f183702956aa4a2116ae75a63cb574b35af8kindest/node:v1.31.14@sha256:6f86cf509dbb42767b6e79debc3f2c32e4ee01386f0489b3b2be24b0a55aac2bNOTE: You must use the
@sha256digest 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
Contributors
Committers for this release:
v0.30.0Compare Source
This is small release containing patched dependencies and Kubernetes 1.34, as well as a bugfix for Kubernetes v1.33.0+ cluster reboots.
Breaking Changes
The default node image is now
kindest/node:v1.34.0@sha256:7416a61b42b1662ca6ca89f02028ac133a309a2a30ba309614e8ec94d976dc5aNew Features
Images pre-built for this release:
kindest/node:v1.34.0@sha256:7416a61b42b1662ca6ca89f02028ac133a309a2a30ba309614e8ec94d976dc5akindest/node:v1.33.4@sha256:25a6018e48dfcaee478f4a59af81157a437f15e6e140bf103f85a2e7cd0cbbf2kindest/node:v1.32.8@sha256:abd489f042d2b644e2d033f5c2d900bc707798d075e8186cb65e3f1367a9d5a1kindest/node:v1.31.12@sha256:0f5cc49c5e73c0c2bb6e2df56e7df189240d83cf94edfa30946482eb08ec57d2NOTE: You must use the
@sha256digest 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
Contributors
Committers for this release:
Configuration
📅 Schedule: (UTC)
🚦 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.
This PR was generated by Mend Renovate. View the repository job log.