[bug] Kubeflow Pipelines may stop working after `March 18, 2025`

[thesuperzapper]

We currently use a number of gcr.io container image repos, and if we dont take action they may stop existing on March 18, 2025. You can see a notice on the top of all gcr.io repos, and Google has published this migration guide which implies that if we don't explicitly migrate to Artifact Registry before May 22, 2025 the images will be deleted.

We need to confirm that all gcr.io accounts which we depend on are going to continue existing (have migrated all images to Artifact Registry), or create a migration and communication plan for users BEFORE next year.

The gcr.io repos we currently use are:

• gcr.io/ml-pipeline/*
  • This one has almost all KFP images in it.
• gcr.io/tfx-oss-public/ml_metadata_store_server
  • This one is the official home of the google/ml-metadata images.
• gcr.io/google-containers/busybox
  • NOTE: this one is probably the most likely to disappear unless we can get confirmation from a Google employee about the status of gcr.io/google-containers.
  • This one disappearing would stop pipelines from running cached steps, because we use this image to run a simple echo command for cached outputs (see https://github.com/kubeflow/pipelines/pull/5184)

---

Impacted by this bug? Give it a 👍.

[thesuperzapper]

@kubeflow/pipelines please take a look at this, we need to confirm that our images will continue existing otherwise all KFP deployments will stop working next year.

[github-actions[bot]]

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.

[KevinGrantLee]

cc @chensun