Dependency update - Golang 1.20.5/1.19.10

[jeremyrickard]

Tracking info

Link to any previous tracking issue: #3025

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

SIG Release Slack thread: https://kubernetes.slack.com/archives/CJH2GBF7Y/p1685659171113989

Work items

• kube-cross image update: Build Go 1.19.10 and Go 1.20.5 images #3105

  • image promotion: Image promotion for build-image v1.27.0-go1.20.5-bullseye.0 / v1.25.0-go1.19.10-bullseye.0 / v1.26.0-go1.19.10-bullseye.0 / v1.23.0-go1.19.10-bullseye.0 / v1.24.0-go1.19.10-bullseye.0 k8s.io#5375

• go-runner image update: Build Go 1.19.10 and Go 1.20.5 images #3105

  • image promotion: Image promotion for build-image v2.3.1-go1.20.5-bullseye.0 / v2.3.1-go1.19.10-bullseye.0 k8s.io#5376

• releng-ci image update: Build Go 1.19.10 and Go 1.20.5 images #3105

  • image promotion: Image promotion for releng 1.20.5-bullseye-0 / 1.19.10-bullseye-0 k8s.io#5377

After kube-cross image promotion

• kubernetes/kubernetes update (master): [go] Bump images, versions and deps to use Go 1.20.5 kubernetes#118507

  Ensure the following have been updated within the PR:

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

After go-runner image promotion

• debian-iptables image update: update debian-iptables and distroless-iptables to use go 1.20.5 #3107

  • image promotion: Image promotion for build-image bullseye-v1.5.7 / v0.2.5 k8s.io#5383

• distroless-iptables image update: update debian-iptables and distroless-iptables to use go 1.20.5 #3107

  • image promotion: Image promotion for build-image bullseye-v1.5.7 / v0.2.5 k8s.io#5383
  • image promotion: Image promotion for build-image v0.2.5 k8s.io#5384

After distroless-iptables image promotion

• kubernetes/kubernetes update (master): bump distroless-iptables to v0.2.5 kubernetes#118541

  Ensure the following have been updated within the PR:

  • distroless-iptables image
  • test image

After kubernetes/kubernetes (master) has been updated

• k8s-cloud-builder image update: Bump k8s-cloud-builder and golang refs to 1.20.5 after k/k update #3108

• k8s-ci-builder image variants update: Bump k8s-cloud-builder and golang refs to 1.20.5 after k/k update #3108

Cherry picks

• Kubernetes 1.27: [release-1.27] releng/go: Update images, deps and ver to Go 1.20.5 kubernetes#118553
• Kubernetes 1.26: [release-1.26] releng/go: Update images, deps and version to go 1.19.10 kubernetes#118555
• Kubernetes 1.25: [release-1.25] releng/go: Update images, deps and ver to go 1.19.10 kubernetes#118556
• Kubernetes 1.24: [release-1.24] releng/go: Update images, deps and ver to go 1.19.10 kubernetes#118557

• publishing bot rule updates for active Golang versions: Update publishing-bot rules for release branches to Go 1.19.10 kubernetes#118629

After kubernetes/kubernetes (release branches) has been updated

• k8s-cloud-builder image update: Bump builders to use Go 1.19.10 #3116

• k8s-ci-builder image variants update: Bump builders to use Go 1.19.10 #3116

• kubekins/krte image variants update: Update kubekins/krte to Go 1.20.5/1.19.10 test-infra#29781

Follow-up items

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

/assign
cc: @kubernetes/release-engineering

[cpanato]

/assign
will help here as well :)

[cpanato]

/priority important-soon

[cpanato]

@jeremyrickard I think we can close, or is anything pending?

[xmudrii]

@cpanato We should consider updating the base image because the latest Go patch releases are using Debian bookworm. There's a Slack thread about that: https://kubernetes.slack.com/archives/CJH2GBF7Y/p1687267181062359

Let's keep this open until we don't make the final decision and then we can create a new tracking issue for base images update.

[cpanato]

sgtm

[xmudrii]

We have #3128 to track base image updates. I think we can close this issue.
/close

[k8s-ci-robot]

@xmudrii: Closing this issue.

In response to this:

We have #3128 to track base image updates. I think we can close this issue.
/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/test-infra repository.