Issues faced in enabling CI for Kubeflow Pipelines on ppc64le & seeking workarounds

[valen-mascarenhas14]

Hello,
We are currently running our KFP e2e tests workflow on a self-hosted runner based on the ppc64le architecture. Out of the 6 tests that run, 2 are failing (frontend-integration test & basic sample test), and we are facing some challenges with certain dependencies that are not supported on ppc64le. I would appreciate any insights or suggestions you might have regarding potential workarounds or alternative approaches.

Specific Issues:
Frontend Integration Test:
The test requires the Selenium-standalone-chrome-gcloud container, which isn't supported on ppc64le. We are considering alternatives such as using another multiarch image or skipping this test altogether.
Question: Has anyone encountered a similar issue, and is there a recommended multiarch alternative we could use?

Database Image:
The MySQL image is not supported on ppc64le, so we have switched to using MariaDB.
Question: Is this a suitable long-term solution, or are there other recommended practices for databases in a ppc64le environment?
Metadata Services:
The Metadata-grpc and Metadata-envoy images are not supported on ppc64le. We are debating whether to skip these images/tests.
Question: Would skipping these components have any significant impact, or is there a better way to handle this limitation?
Any guidance or experience you can share would be greatly appreciated, especially regarding any successful workarounds or multiarch images that could help us maintain compatibility with ppc64le.

Thank you in advance for your assistance.

cc : @rimolive

[valen-mascarenhas14]

@zijianjoy Could you please check this ?