GCB Docker GCloud: Update buildx to v0.19.3.

[Gacko]

No description provided.

[Gacko]

/cc @BenTheElder @aojea

[BenTheElder]

FWIW I strongly recommend leveraging GOTOOLCHAIN to control the version in your repo, which just requires 1.21+ in the image to bootstrap.

we won't be able to have the right default for everyone.

[Gacko]

Well, the only reason I'm proposing this change is that I've seen Go and buildx being bumped regularly from different people in the past. As we from the Ingress NGINX project are using this image and regularly check for updates, I thought it might be a good idea to bump these dependencies to newer versions.

[BenTheElder]

Well, the only reason I'm proposing this change is that I've seen Go and buildx being bumped regularly from different people in the past. As we from the Ingress NGINX project are using this image and regularly check for updates, I thought it might be a good idea to bump these dependencies to newer versions.

Sure, but usually when I see people doing this it's so their builds get a newer go version, and there's a much better way to do that where the version is controlled in the repo being built so upgrading is tested and so you can upgrade more quickly.

[Gacko]

I'm not bumping Go for Ingress NGINX, no worries. I'm bumping it because I'm using this image and am interested in maintaining it and keeping it up-to-date.

If you have concerns about the bump, we can also just go for the latest v1.23 version!

Regarding buildx: I'll check the changelogs now.

[Gacko]

Ok, well. I didn't go into details, but just from the v0.19.0 release notes it might be worth doing this step by step. They seem to introduce deprecations / changes step by step, so I'd suggest going to v0.19.3 in a first step, let people adapt and then move on in a few weeks, so we somewhen catch up with the latest version.

[Gacko]

Any last comments here, @BenTheElder? Shall we merge it as it is right now? Or shall I just leave it and close the PR?

[Gacko]

@BenTheElder I rebased the PR and updated Go to v1.23.9. Any chances to get it merged?

[BenTheElder]

/lgtm
/approve
Sorry, in the future if something gets stuck this long I think it's reasonable to tag in a second approver.
Recently a bit more crunched than usual

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: BenTheElder, Gacko

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 [BenTheElder]

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]

New changes are detected. LGTM label has been removed.

[Gacko]

Well, someone else bumped Go to v1.24.3 on master in the meantime.