Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Merged
merged 1 commit into from
Dec 24, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 24, 2024

This PR contains the following updates:

Package Update Change
kubernetes-sigs/kind minor 0.25.0 -> 0.26.0

Release Notes

kubernetes-sigs/kind (kubernetes-sigs/kind)

v0.26.0

Compare Source

This release brings Kubernetes v1.32.0 to kind by default and fixes kind build node-image for building for Kubernetes releases <v1.31.0 when not building Kubernetes from source (e.g. kind build node-image v1.30.0).

Breaking Changes

  • Removed two deprecated flags that had been printing usage warnings for many releases.
  • The default node image is now Kubernetes v1.32.0: kindest/node:v1.32.0@&#8203;sha256:c48c62eac5da28cdadcf560d1d8616cfa6783b58f0d94cf63ad1bf49600cb027

New Features

  • Updated to go 1.23.4
  • Updated node image dependencies to latest
    • NOTE: you should only be depending on node images to allow kind to create Kubernetes nodes at a given Kubernetes version. The contents of these images are subject to change. However, we have brought everything up to the latest releases which may contain bug fixes.
  • Updated local-path-provisioner to v0.30.0
  • Refreshed Ingres docs to use https://sigs.k8s.io/cloud-provider-kind

Images pre-built for this release:

  • v1.32.0: kindest/node:v1.32.0@&#8203;sha256:c48c62eac5da28cdadcf560d1d8616cfa6783b58f0d94cf63ad1bf49600cb027
  • v1.31.4: kindest/node:v1.31.4@&#8203;sha256:2cb39f7295fe7eafee0842b1052a599a4fb0f8bcf3f83d96c7f4864c357c6c30
  • v1.30.8: kindest/node:v1.30.8@&#8203;sha256:17cd608b3971338d9180b00776cb766c50d0a0b6b904ab4ff52fd3fc5c6369bf
  • v1.29.12: kindest/node:v1.29.12@&#8203;sha256:62c0672ba99a4afd7396512848d6fc382906b8f33349ae68fb1dbfe549f70dec

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 https://github.com/kubernetes-sigs/kind/issues/2718

Fixes

  • Fixed kind build node-image --type=url and kind build node-image --type=release where Kubernetes version is less than v1.31.0
    • E.G. kind build node-image v1.30.0 and kind build node-image https://dl.k8s.io/v1.30.0/kubernetes-server-linux-arm64.tar.gz
    • This fix will only work for standard release tags (and not pre-releases etc), for those continue to use --type=source.
    • v1.31.0+ will work with all build types for all versions

Contributors

Thank you to everyone who contributed to this kind over the years!

Commiters for this release:


Configuration

📅 Schedule: Branch creation - "after 10pm every weekday,before 5am every weekday,every weekend" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, 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 was generated by Mend Renovate. View the repository job log.

@renovate renovate bot enabled auto-merge (squash) December 24, 2024 01:57
@renovate renovate bot merged commit a908330 into main Dec 24, 2024
3 checks passed
@renovate renovate bot deleted the renovate/kubernetes-sigs-kind-0.x branch December 24, 2024 05:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants