Added s390x and ppc64le support

[R3hankhan123]

Description of your changes:
Added multiarch support for s390x and ppc64le by adding Architectural parameters wherever possible in dockerfiles and bash scripts
Checklist:

• The title for your pull request (PR) should follow our title convention. Learn more about the pull request title convention used in this repository.

[google-oss-prow]

Hi @R3hankhan123. Thanks for your PR.

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

[hbelmiro]

/ok-to-test

[hbelmiro]

/retest

[hbelmiro]

/retest

[google-oss-prow]

New changes are detected. LGTM label has been removed.

[R3hankhan123]

@hbelmiro @chensun are the test failing because Kubernetes 1.25 is no longer supported?

[rimolive]

@R3hankhan123 We have an known issue with the current e2e tests so for now we'll need to run them locally to ensure the PR does not introduce any breaking changes.

[hbelmiro]

@R3hankhan123 the e2e test was migrated to GitHub Actions and is working now. Can you please rebase?

/reopen

[google-oss-prow]

@hbelmiro: Reopened this PR.

In response to this:

@R3hankhan123 the e2e test was migrated to GitHub Actions and is working now. Can you please rebase?

/reopen

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.

[dilipgb]

/reopen

[google-oss-prow]

@dilipgb: You can't reopen an issue/PR unless you authored it or you are a collaborator.

In response to this:

/reopen

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.

[R3hankhan123]

/reopen

[google-oss-prow]

@R3hankhan123: Failed to re-open PR: state cannot be changed. There are no new commits on the R3hankhan123:s390x branch.

In response to this:

/reopen

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.

[google-oss-prow]

@R3hankhan123: Reopened this PR.

In response to this:

/reopen

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.

[google-oss-prow]

@R3hankhan123: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
kubeflow-pipeline-e2e-test	0b5e3a3	link	unknown	/test kubeflow-pipeline-e2e-test
kubeflow-pipeline-upgrade-test	21c7017	link	false	/test kubeflow-pipeline-upgrade-test

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.

[R3hankhan123]

@hbelmiro why is the upgrade test and e2e tests failing?

[rimolive]

/rerun-all

[R3hankhan123]

@rimolive @hbelmiro I can see that some github workflows are requiring maintainer's aproval.

[hbelmiro]

/rerun-all

[hbelmiro]

For some reason /rerun-all is not working.
@chensun do you have permission to approve the GitHub workflows to run?

Context: #10981

[R3hankhan123]

Hi @hbelmiro @rimolive @vanpelt
I hope this message finds you well. I noticed that some of the tests for this pull request have not yet been triggered. Could you please let me know when the remaining tests might be triggered?

[hbelmiro]

@R3hankhan123 I don't have permission to trigger them from the GitHub UI.
Due to #10981, /ok-to-test is not triggering the GitHub Actions tests.

Trying once more...

/rerun-all

[R3hankhan123]

@hbelmiro @rimolive any updates on the test that are failing?

[hbelmiro]

@R3hankhan123 please rebase your PR and then we see how it goes.

[R3hankhan123]

/reopen

[google-oss-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign chensun for approval. For more information see the Kubernetes Code Review Process.

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

Needs approval from an approver in each of these files:

• backend/OWNERS
• third_party/OWNERS

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

[google-oss-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign chensun for approval. For more information see the Kubernetes Code Review Process.

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

Needs approval from an approver in each of these files:

• backend/OWNERS
• third_party/OWNERS

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

[R3hankhan123]

@hbelmiro looks like the workflows still arent being triggered automatically