[go] Build go1.16.7 and go1.15.15 images

[cpanato]

What type of PR is this?

/kind feature
/area dependency release-eng/security

What this PR does / why we need it:

Tracking issue: #2196

• [go] go1.16.7 and go1.15.15 updates
• go-runner: Build v2.3.1-go1.16.7-buster.0 and v2.3.1-go1.15.15-buster.0
• releng-ci: build image for go1.16.6 and go1.15.15
• kube-cross: Build v1.16.7-1 and v1.15.15-1 images
• kubepkg/packages-deb: update base image to go1.16.7
• k8s-cloud-builder: Build v1.16.7-1 / v1.15.15-1 / v1.15.15-legacy-1 images

/assign @saschagrunert @puerco @justaugustus
cc @kubernetes/release-engineering

Which issue(s) this PR fixes:

Special notes for your reviewer:

Does this PR introduce a user-facing change?

- [go] go1.16.7 and go1.15.15 updates
- go-runner: Build v2.3.1-go1.16.7-buster.0 and v2.3.1-go1.15.15-buster.0
- releng-ci: build image for go1.16.6 and go1.15.15
- kube-cross: Build v1.16.7-1 and v1.15.15-1 images
- kubepkg/packages-deb: update base image to go1.16.7
- k8s-cloud-builder: Build v1.16.7-1 / v1.15.15-1 / v1.15.15-legacy-1 images

[cpanato]

/priority important-soon

[cpanato]

will check the k8s-cloud-builder, will drop some changes from this PR and open a follow up

[justaugustus]

will check the k8s-cloud-builder, will drop some changes from this PR and open a follow up

Yep. k8s-cloud-builder should not be bumped until after the other images have been promoted and the appropriate changes have been made to master (to prevent drift between the cross env in k/k presubmits and GCB releases).

The only exception to this would be a "next candidate" release, like go1.17rc2 (#2190), where we know the new go version won't be in use yet.

nit: the commit message for releng-ci image should mention go1.16.7, not go1.16.6

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cpanato, justaugustus, saschagrunert

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [cpanato,justaugustus,saschagrunert]
• images/build/OWNERS [cpanato,justaugustus,saschagrunert]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[k8s-ci-robot]

@cpanato: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Rerun command
pull-release-image-k8s-cloud-builder	f82dd59	link	/test pull-release-image-k8s-cloud-builder

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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. I understand the commands that are listed here.

[cpanato]

looks like some rate limit, will wait a bit and retest it

[cpanato]

/test pull-release-image-go-runner

[cpanato]

/test pull-release-integration-test