Migration of image hosting from gcr.io to Artifact Registry

[akdigitalself]

Ask your question here:

As per this announcement, after May 15, 2024. Google Cloud projects without previous usage of Container Registry will only support hosting and managing images for the gcr.io domain in Artifact Registry.

The images in v1.10.1 are using gcr.io. I didn't find any open or closed issue indicating the migration to Container Registry. So I am creating this issue to track the ETA of this migration. Thanks!

[dprotaso]

/assign @upodroid @kvmware

[upodroid]

I saw that announcement from Google but it doesn't affect us as GCR is enabled in knative-releases and knative-nightly. That being said, I'll put together a plan for migrating to Artifact Registry.

GCR has been EoL for some time and this part of that journey.

/lifecycle frozen
/area infra

[knative-prow]

@upodroid: The label(s) area/infra cannot be applied, because the repository doesn't have them.

In response to this:

I saw that announcement from Google but it doesn't affect us as GCR is enabled in knative-releases and knative-nightly. That being said, I'll put together a plan for migrating to Artifact Registry.

GCR has been EoL for some time and this part of that journey.

/lifecycle frozen
/area infra

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.

[upodroid]

/transfer knative/infra

[krsna-m]

@upodroid are we done with this issue now?

[upodroid]

No, we completed the migration for the internal CI. Our public images for end users need to be planned and started soon.

[thesuperzapper]

@upodroid did this migration ever end up happening, because it's not clear that the images will still exist after 2025 otherwise?