Dependency update - Golang 1.24.0

[liggitt]

Tracking info

Link to any previous tracking issue: #3650

Golang mailing list announcement:

SIG Release Slack thread:

Work items for go1.24rc1

Golang mailing list announcement: https://groups.google.com/g/golang-announce/c/vYMfuq_XO6w/m/YlJ1SR6lAQAJ

• kube-cross, go-runner, releng-ci image updates: golang: Build 1.24rc1 images #3872

  • kube-cross image promotion: Image promotion for build-image v1.33.0-go1.24rc1-bullseye.0 k8s.io#7674
  • go-runner image promotion: Image promotion for build-image v2.4.0-go1.24rc1-bookworm.0 k8s.io#7675
  • releng-ci image promotion: not promoting this image

After go-runner image promotion

• distroless-iptables image update: build distroless-iptables with go1.24rc1 #3884

  • image promotion: Image promotion for build-image v0.7.0 k8s.io#7687

Work items for go1.24rc2

Golang mailing list announcement: https://groups.google.com/g/golang-announce/c/L8jWYHEfOlQ

• kube-cross, go-runner, releng-ci image updates: golang: Build 1.24rc2 images #3904

  • kube-cross image promotion: Image promotion for build-image v1.33.0-go1.24rc2-bullseye.0 k8s.io#7756
  • go-runner image promotion: Image promotion for build-image v2.4.0-go1.24rc2-bookworm.0 k8s.io#7755
  • releng-ci image promotion: not promoting this image

After go-runner image promotion

• distroless-iptables image update: build distroless-iptables with go1.24rc2 #3910

  • image promotion: Image promotion for build-image v0.7.1 k8s.io#7765

Work items for go1.24rc3

Golang mailing list announcement: https://groups.google.com/g/golang-announce/c/w2gBC3sJibs/m/bUz6JjCCAAAJ

• kube-cross, go-runner, releng-ci image updates: golang: Build 1.24rc3 images #3911

  • kube-cross image promotion: Image promotion for build-image v1.33.0-go1.24rc3-bullseye.0 k8s.io#7768
  • go-runner image promotion: Image promotion for build-image v2.4.0-go1.24rc3-bookworm.0 k8s.io#7769
  • releng-ci image promotion: not promoting this image

After go-runner image promotion

• distroless-iptables image update: bump distroless-iptables to use go1.22.12 and go1.23.6 and go1.24rc3 #3918

  • image promotion: Image promotion for build-image v0.7.2 / v0.6.8 / v0.5.13 k8s.io#7773

Work items for go1.24

Golang mailing list announcement: https://groups.google.com/g/golang-announce/c/_G2hEiKx8SE/m/5uEc3vwVAgAJ

• kube-cross, go-runner, releng-ci image updates: golang: Build 1.24.0 images #3930

  • kube-cross image promotion: Image promotion for build-image v1.33.0-go1.24.0-bullseye.0 k8s.io#7811
  • go-runner image promotion: Image promotion for build-image v2.4.0-go1.24.0-bookworm.0 k8s.io#7813
  • releng-ci image promotion: Image promotion for releng 1.24.0-bookworm-0 k8s.io#7814

After go-runner image promotion

• distroless-iptables image update: build distroless-iptables with go1.24.0 #3932

  • image promotion: Image promotion for build-image v0.7.3 k8s.io#7815

After kube-cross and distroless-iptables image promotions

• kubernetes/kubernetes update (master): [go] Bump images, dependencies and versions to go 1.24.0 kubernetes#129688

  Ensure the following have been updated within the PR:

  • .go-version file
  • kube-cross image
  • go-runner image
  • distroless-iptables image
  • publishing bot rules
  • test image

Note
This update may require an update to go.sum files, for example: kubernetes/kubernetes#118507
This will require an API Review approval.

After kubernetes/kubernetes (master) has been updated

• k8s-cloud-builder and k8s-ci-builder image updates: build k8s-cloud-builder and k8s-ci-builder for go1.24 #3942

• kubekins/krte image variants update: update kubekins to go1.24.0 test-infra#34425

Follow-up items

• Ensure the Golang issue template is updated with any new requirements

/assign
cc: @kubernetes/release-engineering

[liggitt]

Tracking PRs related to go1.24 that we would need to pick to release branches as part of an eventual update to go1.24:

• Go vet fixes for gotip kubernetes#127422

  • 1.32: Go vet fixes for gotip kubernetes#127422
  • 1.31: Automated cherry pick of #127422: Fix Go vet errors for master golang kubernetes#129519
  • 1.30: Automated cherry pick of #127422: Go vet fixes for gotip kubernetes#129521
  • 1.29: Automated cherry pick of #127422: Go vet fixes for gotip kubernetes#129524
  • 1.28: EoL

• [go1.24] webhook: alter regex to account for x509sha1 GODEBUG removal kubernetes#129430

  • 1.32: [go1.24][1.32] webhook: alter regex to account for x509sha1 GODEBUG removal kubernetes#129495
  • 1.31: [go1.24][1.31] webhook: alter regex to account for x509sha1 GODEBUG removal kubernetes#129494
  • 1.30: [go1.24][1.30] webhook: alter regex to account for x509sha1 GODEBUG removal kubernetes#129493
  • 1.29: [go1.24][1.29] webhook: alter regex to account for x509sha1 GODEBUG removal kubernetes#129492
  • 1.28: EoL

• [go] Bump images, dependencies and versions to go 1.24.0 kubernetes#129688 (only the Bump hack/tools to github.com/golangci/golangci-lint 1.64.5 for go 1.24 and golangci-lint: temporarily suppress known issues in the code base commits)

  • 1.32:
  • 1.31:
  • 1.30:
  • 1.29:

---

Tracking verification of conditions for bumping go1.21 on release branches:

• ~2025-05: 3 months after go 1.24 release (ETA 2025-02)
• ~2025-05: 1 month after Kubernetes 1.33 release on go1.24 (ETA 2025-04-15)
• no regressions relative to go 1.24 known to impact Kubernetes
• pass unit and integration tests with both go 1.24 and the original go version for the release branch
  • 1.32:
  • 1.31:
  • 1.30:
  • 1.29:
• any behavior changes in go 1.24 are mitigated to preserve existing behavior without requiring action by Kubernetes end-users

---

Tracking the PR that actually bumps to go1.24:

• 1.32:
• 1.31:
• 1.30:
• 1.29:

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[cpanato]

/remove-lifecycle stale
/assign