Updated QEMU image and added cross build support for s390x kind binary and associated images

[guirish]

Updated QEMU image to tonistiigi/binfmt:qemu-v6.1.0 and added cross build support for s390x kind binary and associated images.

[k8s-ci-robot]

Thanks for your pull request. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please follow instructions at https://git.k8s.io/community/CLA.md#the-contributor-license-agreement to sign the CLA.

It may take a couple minutes for the CLA signature to be fully registered; after that, please reply here with a new comment and we'll verify. Thanks.

---

• If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA data and verify that your email is set on your git commits.
• If you signed the CLA as a corporation, please sign in with your organization's credentials at https://identity.linuxfoundation.org/projects/cncf to be authorized.
• If you have done the above and are still having issues with the CLA being reported as unsigned, please log a ticket with the Linux Foundation Helpdesk: https://support.linuxfoundation.org/
• Should you encounter any issues with the Linux Foundation Helpdesk, send a message to the backup e-mail support address at: [email protected]

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.

[k8s-ci-robot]

Hi @guirish. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: guirish
To complete the pull request process, please assign amwat after the PR has been reviewed.
You can assign the PR to them by writing /assign @amwat in a comment when ready.

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

Needs approval from an approver in each of these files:

• OWNERS

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

[aojea]

Please sign the CLA @guirish

[guirish]

"I signed it"

[BenTheElder]

TODO (unrelated to this PR): add ppc64le back to images/Makefile.common.in or drop it here.

[BenTheElder]

/ok-to-test

[BenTheElder]

The commit in this PR is not associated with your GitHub account (I think maybe email not included?), the CNCF CLA bot requires that:

1. You have a signed CLA associated with your GitHub account
2. Your commits are associated with GitHub accounts that have signed the CLA (some of them can be from others but they must also be accounts that meet 1))

Right now it's failing on 2).

[BenTheElder]

#23 2.340 go: github.com/coreos/[email protected]: Get "https://proxy.golang.org/github.com/coreos/go-iptables/@v/v0.4.5.mod": tls: invalid signature by the server certificate: ECDSA verification failure
#23 ERROR: process "/bin/sh -c go mod download" did not complete successfully: exit code: 1

https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/kubernetes-sigs_kind/2494/pull-kind-build/1447949063788957696 🤔

[aojea]

The file https://github.com/kubernetes-sigs/kind/blob/main/images/base/Dockerfile has to be updated to download the corresponding dependencies

[aojea]

it only needs

diff --git a/images/base/update-shasums.sh b/images/base/update-shasums.sh
index 8876e833..86c30ac8 100755
--- a/images/base/update-shasums.sh
+++ b/images/base/update-shasums.sh
@@ -39,6 +39,7 @@ ARCHITECTURES=(
     "amd64"
     "arm64"
     "ppc64le"
+    "s390x"
 )
 
 echo

[aojea]

I'll take it from here, and add it for the image base bump

[aojea]

/hold
part of #2465

[BenTheElder]

rebased merged in #2465

thanks!

[rohitsakala]

Hi, which kind version and on what date will have s390x support ? @BenTheElder Thanks :)

[BenTheElder]

In the next release there will be very limited support in which the non-configurable development images are s390x, and the binary is s390x. There is no intention to build node images for s390x at this time, nor CI / testing.
There is no release date yet, releases and in general all work on this repo are best-effort.

[BenTheElder]

Also noting: I've had builds hang on s390x a few times now :/
These issues + limited-to-nonexistent demand are why PPC64LE never made it to full support.