golang: Build 1.25.0 images

[cpanato]

What type of PR is this?

/kind feature

What this PR does / why we need it:

• golang: Build 1.25.0 images

/hold
/assign @saschagrunert @ameukam @puerco @MadhavJivrajani
cc @kubernetes/release-managers @liggitt

Which issue(s) this PR fixes:

xref #3957

Special notes for your reviewer:

Does this PR introduce a user-facing change?

golang: Build 1.25.0 images

[ameukam]

/lgtm
we may want to think about Debian Trixie: https://wiki.debian.org/DebianTrixie

[cpanato]

lets look on that after this

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cpanato, 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,saschagrunert]

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

[saschagrunert]

/retest

[cpanato]

humm

docker.io/library/golang:1.25.0-bullseye

does not exist only

1.25.0-bookworm
or 
1.25.0-trixie

But the image that is using it is kube-cross, and iffi, remember correctly, the bookworm has a breaking change for the kubelet

Should we upgrade to Bookworm and see what the breaks are, or move to Trixie?

cc @dims @saschagrunert @liggitt

[saschagrunert]

Related to #3246

The reason to use bullseye was the lower glibc version constraint (2.31). Now using bookworm will increase that version to 2.36 and trixie ships 2.41.

[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	Required	Rerun command
pull-release-image-kube-cross	985d166	link	true	/test pull-release-image-kube-cross

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