Dependency update - Golang 1.26.1/1.25.8

[cpanato]

Tracking info

Link to any previous tracking issue: #4265

Golang mailing list announcement: https://groups.google.com/g/golang-announce/c/EdhZqrQ98hk/m/41DopX_WAAAJ

SIG Release Slack thread:

Work items

• kube-cross, go-runner, releng-ci image updates: build kube-cross, go-runner, releng-ci with golang 1.26.1/1.25.8 #4327

  • kube-cross image promotion: Image promotion for build-image v1.36.0-go1.26.1-bullseye.0 / v1.35.0-go1.25.8-bullseye.0 k8s.io#9234
  • go-runner image promotion: Image promotion for build-image v2.4.0-go1.26.1-bookworm.0 / v2.4.0-go1.25.8-bookworm.0 k8s.io#9233
  • releng-ci image promotion: Image promotion for releng 1.26.1-trixie-0 / 1.25.8-trixie-0 k8s.io#9232

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

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

[xmudrii]

Superseded by #4365
/close

[k8s-ci-robot]

@xmudrii: Closing this issue.

Details

In response to this:

Superseded by #4365
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.