build and publish `ml_metadata_store_server` container image for ARM64

[thesuperzapper]

Description

Right now, the gcr.io/tfx-oss-public/ml_metadata_store_server container image is the only image used in Kubeflow which is not published for both amd64 AND arm64. This means that Kubeflow 1.8 still can not properly run on ARM clusters.

I have made a PR upstream in google/ml-metadata to get the builds working for ARM64:

• allow building ml_metadata_store_server image on ARM64 google/ml-metadata#188

We need to work with the ml-metadata team to review/merge it and then set up a process to also push the ARM version of that image to GCR.

EDIT: I was incorrect about this being the "only one" but I think this must be the only one that does not work at all under Rosetta emulation (but either way, we need to fix this one too as we also push native arm images for the others). I have raised a separate issue to track fixing the other images:

• build and publish ARM images for kubeflow pipelines  #10309

---

Love this idea? Give it a 👍.

[thesuperzapper]

/cc @chensun @zijianjoy

[thesuperzapper]

For those who want to test, I have made a forked repo in the deployKF org with the ARM versions of the gcr.io/tfx-oss-public/ml_metadata_store_server image. You can test a patched version of ml-metdata version 1.14.0 by using the following container:

• ghcr.io/deploykf/ci/ml_metadata_store_server:sha-cad0c56
• ghcr.io/deploykf/ml_metadata_store_server:1.14.0-deploykf.0
  • (EDIT: use this one now that we have a proper release)

Note, building under emulation on GitHub actions took about 5 hours:

• https://github.com/deployKF/ml-metadata/actions/runs/7188243840/job/19577521345

[xixici]

Great. I pull this image and run it correctly. Then, I am finding gcr.io/ml-pipeline/metadata-writer and gcr.io/ml-pipeline/metadata-envoy with ARM version.

[thesuperzapper]

@xixici can you confirm what you are saying?

Because gcr.io/ml-pipeline/metadata-writer:2.0.5 and gcr.io/ml-pipeline/metadata-envoy:2.0.5 (and all other versions) are only published for ADM64.

I assume you mean that they work via Rosetta Emulation on a MacBook?

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[github-actions]

This issue has been automatically closed because it has not had recent activity. Please comment "/reopen" to reopen it.

[thesuperzapper]

/reopen

[google-oss-prow]

@thesuperzapper: Reopened this issue.

Details

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/test-infra repository.

[thesuperzapper]

Clearly, this is going to take some time, so I will prevent the bot from closing it.

/lifecycle frozen