test: use newer test images for better s390x coverage

[yselkowitz]

What type of PR is this?

/kind bug
/kind failing-test

What this PR does / why we need it:

This uses the new image versions with s390x enabled via #102785 so that the tests which depend thereon will pass on s390x.

Does this PR introduce a user-facing change?

NONE

/cc @mkumatag

[k8s-ci-robot]

@yselkowitz: This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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]

Hi @yselkowitz. Thanks for your PR.

I'm waiting for a kubernetes 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.

[yselkowitz]

@mkumatag what is missing to get the new versions from #102785 built and pushed, so that we can proceed with this?

[mkumatag]

@mkumatag what is missing to get the new versions from #102785 built and pushed, so that we can proceed with this?

I see some post-merge failure for one of the job, anyways lemme trigger the tests and see how it goes

/ok-to-test

[mkumatag]

we need to bump the images here as well - https://github.com/kubernetes/k8s.io/blob/main/k8s.gcr.io/images/k8s-staging-e2e-test-images/images.yaml

[yselkowitz]

we need to bump the images here as well - https://github.com/kubernetes/k8s.io/blob/main/k8s.gcr.io/images/k8s-staging-e2e-test-images/images.yaml

OK, if you can get the post-merge job to run again to build node-perf/npb-is, then I can post the PR for these and the glusterdynamic-provision promotions.

[mkumatag]

we need to bump the images here as well - https://github.com/kubernetes/k8s.io/blob/main/k8s.gcr.io/images/k8s-staging-e2e-test-images/images.yaml

OK, if you can get the post-merge job to run again to build node-perf/npb-is, then I can post the PR for these and the glusterdynamic-provision promotions.

PR submitted for the promotion here - kubernetes/k8s.io#2974

[mkumatag]

/retest

[mkumatag]

/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mkumatag, yselkowitz

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:

• test/utils/image/OWNERS [mkumatag]

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

[yselkowitz]

/retest