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

• kube-cross, go-runner, releng-ci image updates:

  • kube-cross image promotion:
  • go-runner image promotion:
  • releng-ci image promotion:

After go-runner image promotion

• distroless-iptables image update:

  • image promotion:

After kube-cross and distroless-iptables image promotions

• kubernetes/kubernetes update (master):

  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:

• kubekins/krte image variants update:

Cherry picks

• Kubernetes 1.y-1:
• Kubernetes 1.y-2:
• Kubernetes 1.y-3:

• publishing bot rule updates for active Golang versions:

After kubernetes/kubernetes (release branches) has been updated

• k8s-cloud-builder and k8s-ci-builder image updates:

• kubekins/krte image updates:

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.20:

• Go vet fixes for gotip kubernetes#127422
  • 1.32:
  • 1.31:
  • 1.30:
  • 1.29:
  • 1.28:

---

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