Build s390x binaries using musl libc

[saschagrunert]

What type of PR is this?

/kind bug

What this PR does / why we need it:

Building using musl until NixOS/nixpkgs#306473 is resolved.

Which issue(s) this PR fixes:

Refers to #7911

Special notes for your reviewer:

None

Does this PR introduce a user-facing change?

Using musl libc for s390x until the static glibc issue is resolved.

[kannon92]

xref: NixOS/nixpkgs#306473

[kwilczynski]

/approve
/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

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

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

[saschagrunert]

/override ci/prow/ci-cgroupv2-e2e
/override ci/prow/ci-rhel-critest

[openshift-ci]

@saschagrunert: Overrode contexts on behalf of saschagrunert: ci/prow/ci-cgroupv2-e2e, ci/prow/ci-rhel-critest

In response to this:

/override ci/prow/ci-cgroupv2-e2e
/override ci/prow/ci-rhel-critest

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.

[saschagrunert]

/cherry-pick release-1.29

[saschagrunert]

/cherry-pick release-1.28

[openshift-cherrypick-robot]

@saschagrunert: #8070 failed to apply on top of branch "release-1.29":

Applying: Build s390x binaries using musl libc
Using index info to reconstruct a base tree...
M	nix/derivation.nix
Falling back to patching base and 3-way merge...
Auto-merging nix/derivation.nix
CONFLICT (content): Merge conflict in nix/derivation.nix
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 Build s390x binaries using musl libc
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.29

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.

[openshift-cherrypick-robot]

@saschagrunert: #8070 failed to apply on top of branch "release-1.28":

Applying: Build s390x binaries using musl libc
Using index info to reconstruct a base tree...
M	nix/derivation.nix
Falling back to patching base and 3-way merge...
Auto-merging nix/derivation.nix
CONFLICT (content): Merge conflict in nix/derivation.nix
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 Build s390x binaries using musl libc
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.28

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.