Update kubernetes dependencies#76
Closed
renovate-for-pdx[bot] wants to merge 1 commit intomainfrom
Closed
Conversation
Contributor
Author
ℹ️ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
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
3 participants
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:
v0.34.3→v0.35.3v0.34.3→v0.35.3v0.34.3→v0.35.3v1.34.0→v1.34.3v1.33.4→v1.33.7v1.32.8→v1.32.11v0.23.2→v0.23.31.34.1→1.35.0v0.19.0→v0.20.1v0.30.0→v0.31.0v4.10.1→v4.13.1v5.8.0→v5.8.11.34.3→1.35.3v0.22.4→v0.23.3Renovate will not update the Kubernetes minor version automatically.
Please check the Kubernetes release notes and update the version manually if needed:
Release Notes
kubernetes/api (k8s.io/api)
v0.35.3Compare Source
v0.35.2Compare Source
v0.35.1Compare Source
v0.35.0Compare Source
v0.34.6Compare Source
v0.34.5Compare Source
v0.34.4Compare Source
kubernetes/apimachinery (k8s.io/apimachinery)
v0.35.3Compare Source
v0.35.2Compare Source
v0.35.1Compare Source
v0.35.0Compare Source
v0.34.6Compare Source
v0.34.5Compare Source
v0.34.4Compare Source
kubernetes/client-go (k8s.io/client-go)
v0.35.3Compare Source
v0.35.2Compare Source
v0.35.1Compare Source
v0.35.0Compare Source
v0.34.6Compare Source
v0.34.5Compare Source
v0.34.4Compare Source
kubernetes-sigs/controller-runtime (kubernetes-sigs/controller-runtime/setup-envtest)
v0.23.3Compare Source
What's Changed
Full Changelog: kubernetes-sigs/controller-runtime@v0.23.2...v0.23.3
kubernetes-sigs/controller-tools (kubernetes-sigs/controller-tools)
v1.35.0Compare Source
kubernetes-sigs/kind (kubernetes-sigs/kind)
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:
kubernetes-sigs/kubebuilder (kubernetes-sigs/kubebuilder)
v4.13.1Compare Source
🚀 Keep Your Scaffold Updated
The migration guide covers upgrading from
anyversion to thelatest, including AI-assisted helpers/commands for legacy scaffolds that may require manual steps. For the smoothest path, enable the AutoUpdate Plugin (uses GitHub Actions) or runkubebuilder alpha updatelocally—both use the same update logic. The other options are primarily for older projects missingcliVersionin thePROJECTfile as a one-time step to reach a supported version; after that, you can rely on these workflows for ongoing updates.✨ Upgrades
v1.19.4tov1.20.0(#5531)v0.23.1tov0.23.3(#5532)🐛 Bug Fixes
What's Changed
1.19.4to1.20.0by @camilamacedo86 in #55310.23.1to0.23.3by @camilamacedo86 in #5532New Contributors
Full Changelog: kubernetes-sigs/kubebuilder@v4.13.0...v4.13.1
v4.13.0Compare Source
🚀 Keep Your Scaffold Updated
The migration guide covers upgrading from
anyversion to thelatest, including AI-assisted helpers/commands for legacy scaffolds that may require manual steps. For the smoothest path, enable the AutoUpdate Plugin (uses GitHub Actions) or runkubebuilder alpha updatelocally—both use the same update logic. The other options are primarily for older projects missingcliVersionin thePROJECTfile as a one-time step to reach a supported version; after that, you can rely on these workflows for ongoing updates.✨ Upgrades
v1.19.3tov1.19.4(#5509)✨ New Features
manager.envOverridesto support overriding manager environment variables via Helm CLI (e.g.--set manager.envOverrides.LOG_LEVEL=debug) (#5495)🐛 Bug Fixes
manager.replicasso values fromvalues.yamlare correctly applied in the chart template (#5494)editwith go/v4 + helm/v2-alpha) (#5506)0644, directories:0755) (#5508)🎉 Thanks to all contributors!
What's Changed ( Full Changelog )
New Contributors
Full Changelog: kubernetes-sigs/kubebuilder@v4.12.0...v4.13.0
v4.12.0Compare Source
🚀 Keep Your Scaffold Updated
The migration guide covers upgrading from
anyversion to thelatest, including AI-assisted helpers/commands for legacy scaffolds that may require manual steps. For the smoothest path, enable the AutoUpdate Plugin (uses GitHub Actions) or runkubebuilder alpha updatelocally—both use the same update logic. The other options are primarily for older projects missingcliVersionin thePROJECTfile as a one-time step to reach a supported version; after that, you can rely on these workflows for ongoing updates.✨ Upgrades
v2.7.2tov2.8.1. (#5403, #5481)v1.19.2tov1.19.3. (#5431)v0.20.0tov0.20.1(#5475)5.7.1to5.8.1. (#5412, #5481)✨ New features
Chart.yamlmetadata. (#5414)Notes.txt. (#5392).devcontainer/post-install.shand enhance script. (#5394, #5435)--namespaced. The flag is valid for init and edit subcommands (#5411, #5482, #5480)--multigroupflag to init subcommand. Now you can initialize a project with this layout (#5440)--merge-messageand flag--conflict-messageto allow customise commit messages. (#5429, #5479)🐛 Bug fixes
.Values.webhook.enableconditional. (#5413)crd.keepto correctly add thehelm.sh/resource-policy: keepannotation to generated CRDs (#5472)helm/v1-alphaplugin entry from PROJECT file whenhelm/v2-alphais used. (#5436)--helpcommand was used with--pluginsand improve output to show the available help plugins per subcommand. (#5448)🎉 Thanks to all contributors!
What's Changed ( Full Changelog )
5.7.1to5.8.0by @camilamacedo86 in #54125.8.0to5.8.1by @camilamacedo86 in #5481New Contributors
Full Changelog: kubernetes-sigs/kubebuilder@v4.11.1...v4.12.0
v4.11.1Compare Source
🚀 Keep Your Scaffold Updated
The migration guide covers upgrading from
anyversion to thelatest, including AI-assisted helpers/commands for legacy scaffolds that may require manual steps. For the smoothest path, enable the AutoUpdate Plugin (uses GitHub Actions)) or runkubebuilder alpha updatelocally—both use the same update logic. The other options are primarily for older projects missingcliVersionin thePROJECTfile as a one-time step to reach a supported version; after that, you can rely on these workflows for ongoing updates.🐛 Bug fixes
controller-runtimefromv0.23.0tov0.23.1. For further information, see its release notes.(#5402)extrasdirectory. (#5389)versionsubcommand for improved readability and consistency. (#5236)cmdpackage underinternalto improve encapsulation and API boundaries. (#5400)Note: If you did not upgrade your project to v4.11.0, please make sure to review its release notes, as they contain important major changes that also apply to this release.
🎉 Thanks to all contributors!
What's Changed (Full Changelog)
v0.23.0tov0.23.1by @camilamacedo86 in #5402Full Changelog: kubernetes-sigs/kubebuilder@v4.11.0...v4.11.1
v4.11.0Compare Source
🚀 Keep Your Scaffold Updated
🎉 Our migration guide was fully updated to help you upgrade from
anyversion to thelatest. It also now includes AI migration helpers/commands to guide upgrades for old scaffolds where manual steps are required. See the migrations guidance.controller-runtime
v0.23.0upgrade (v0.22.4→v0.23.0)This release updates Kubebuilder scaffolding to match controller-runtime v0.23.0. This version includes breaking changes that impact generated projects:
tools/recordtotools/eventstestEnv.Stop()now requires anEventuallywrapper for graceful shutdownIf you use the Helm plugin to distribute your project
This release includes major Helm plugin changes (community-raised fixes and improvements have been addressed). Please update your project:
If you use helm/v1-alpha: upgrade to helm/v2-alpha. Using kubebuilder alpha generate or kubebuilder alpha update will re-scaffold your project and auto-migrate Helm v1 → v2.
If you use helm/v2-alpha and you update manually (not via kubebuilder alpha generate / kubebuilder alpha update, or neither has the AutoUpdate Plugin configured), then re-generate the chart with all fixes:
If you have customisations, back up your current Helm chart first so you can re-apply them on top of the latest version.
Tip: Check the `PR
Configuration
📅 Schedule: (in timezone Asia/Tokyo)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Renovate Bot.