update golang to 1.21.1

[jacob-delgado]

No description provided.

[jacob-delgado]

/cherry-pick release-1.18

[istio-testing]

@jacob-delgado: once the present PR merges, I will cherry-pick it on top of release-1.18 in a new PR and assign it to you.

In response to this:

/cherry-pick release-1.18

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.

[jacob-delgado]

/cherry-pick release-1.19

[istio-testing]

@jacob-delgado: once the present PR merges, I will cherry-pick it on top of release-1.19 in a new PR and assign it to you.

In response to this:

/cherry-pick release-1.19

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.

[ericvn]

It looks like you are cherry-picking to 1.18 but you also have a PR for updating it's 1.20 version.

[ericvn]

It looks like you are cherry-picking to 1.18 but you also have a PR for updating it's 1.20 version.

#2650

[jacob-delgado]

/retest

[istio-testing]

@jacob-delgado: #2652 failed to apply on top of branch "release-1.18":

Applying: update golang to 1.21.1
Using index info to reconstruct a base tree...
M	docker/build-tools/Dockerfile
Falling back to patching base and 3-way merge...
Auto-merging docker/build-tools/Dockerfile
CONFLICT (content): Merge conflict in docker/build-tools/Dockerfile
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 update golang to 1.21.1
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherry-pick release-1.18

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.

[istio-testing]

@jacob-delgado: new issue could not be created for failed cherrypick: status code 410 not one of [201], body: {"message":"Issues are disabled for this repo","documentation_url":"https://docs.github.com/v3/issues/"}

In response to this:

/cherry-pick release-1.18

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.

[istio-testing]

In response to a cherrypick label: new pull request created: #2653