Dependency update - Golang 1.16

[justaugustus]

Tracking info

go1.16 was released on 2/16: https://groups.google.com/g/golang-announce/c/q-exD-8mG3w
go1.16rc1 was released on 1/28: https://groups.google.com/g/golang-announce/c/U_FUHY4wuSc
go1.16beta1 was released on 12/17: https://groups.google.com/g/golang-announce/c/2-Rj3P5uRLs

As Kubernetes 1.20 has already been released, we can get started on pulling in the Golang prereleases.

Golang mailing list announcement:

SIG Release Slack thread: https://kubernetes.slack.com/archives/C2C40FMNF/p1610074100305000

Pre-work: k/repo-infra updates

• Update k/repo-infra to bazel 3.4.1, [email protected]: kubernetes/repo-infra@v0.1.3...v0.2.0
• Update k/k to bazel 3.4.1 and k/[email protected]: build: Update bazel to 3.4.1 and k/repo-infra to v0.2.0 kubernetes#96011

Work items for go1.16rc1

• kube-cross image update: [go1.16] Build go1.16rc1 images #1882

  • image promotion: releng: go1.16rc1 and etcd image promotions k8s.io#1591

• go-runner image update: [go1.16] Build go1.16rc1 images #1882

  • image promotion: releng: Promote go-runner:buster-v2.3.0 k8s.io#1598

• vulndash image update: [go1.16] Build go1.16rc1 images #1882

  • image promotion: releng: go1.16rc1 and etcd image promotions k8s.io#1591

• releng-ci image update: [go1.16] Build go1.16rc1 images #1882

  • image promotion: releng: go1.16rc1 and etcd image promotions k8s.io#1591

During kube-cross image promotion

• kubernetes/repo-infra update: fix go_genrule for 1.16 repo-infra#229 No longer required as bazel has been removed

• kubernetes/repo-infra release cut: https://github.com/kubernetes/repo-infra/releases/tag/v0.2.1 No longer required as bazel has been removed

After kube-cross image promotion

• kubernetes/kubernetes update (master): [go1.16] Update to go1.16 kubernetes#98572

  Ensure the following have been updated within the PR:

  • rules_go No longer required as bazel has been removed
  • kube-cross image
  • go-runner image
  • publishing bot rules

After kubernetes/kubernetes has been updated

• k8s-cloud-builder image update: Update k8s-cloud-builder to v1.16.0-1 and k8s-ci-builder to use go1.16 #1932

• k8s-ci-builder image variants update: Update k8s-cloud-builder to v1.16.0-1 and k8s-ci-builder to use go1.16 #1932

• kubekins/krte image variants update: kubernetes-verify: Use kubekins-e2e master variant for blocking jobs test-infra#21129

Cherry picks

N/A

Follow-up items

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

/assign
cc: @kubernetes/release-engineering

[liggitt]

cc @kubernetes/sig-scalability @wojtek-t in case there are any scale impacts we should be keeping an eye on

[wojtek-t]

There seem to be some regression in early December. We're working with golang folks to figure that out.
@tosi3k - can you please file an issue for that so that it's possible to track it?

[tosi3k]

Done: kubernetes/kubernetes#97846.

[justaugustus]

(I'll start moving on this again once go1.16rc1 is out. signal: golang/go#43253)

There seem to be some regression in early December. We're working with golang folks to figure that out.
@tosi3k - can you please file an issue for that so that it's possible to track it?

@wojtek-t @tosi3k -- Any updates re: this (👇🏾) regression?

Done: kubernetes/kubernetes#97846.

[justaugustus]

Echoing the scalability update from kubernetes/kubernetes#97846 (comment):

It seems we're mostly understanding the issue - we're trying to confirm last remaining details.

But the bottomline is that it doesn't seem to be golang-related - golang seem to be fine.

We will update the issue once we confirm the remaining details.

and kubernetes/kubernetes#97846 (comment):

To add a bit more details to it - there were some internal changes which resulted in some underlying machine architecture having much more predictible networking characteristics than others.

With our jobs requiring high predictability, the recommendation from Google networking engineers was to simply migrate the jobs to new enough architecture (Skylake+) which we did in: kubernetes/test-infra#20584

And that fixed our problems.

Closing this one as addressed.

[nikhita]

go 1.16 tripped the publishing-bot: kubernetes/kubernetes#56876 (comment)

Looks like it's hitting golang/go#44129 or something similar. I'll take a look at this tomorrow.

[justaugustus]

Thanks @nikhita! Keep us posted :)

[nikhita]

Looks like it's hitting golang/go#44129 or something similar. I'll take a look at this tomorrow.

Created kubernetes/kubernetes#99674 to fix this

[justaugustus]

We're all set here.
go1.16.1 tracking is here: #1936

/close

[k8s-ci-robot]

@justaugustus: Closing this issue.

In response to this:

We're all set here.
go1.16.1 tracking is here: #1936

/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.