Migrate away from GCR

[ameukam]

What would you like to be added:

Part of:

• GCR to Artifact Registry tracking k8s.io#1343

Migrate exiting GCR container registries used for the release process to GCP Artifact registry.

Why is this needed:

GCR will be shutdown in 2025:

March 18, 2025: You will no longer be able to push new images to the Container Registry.
April 22, 2025: You will lose access to existing images in the Container Registry. To maintain access, you must copy them to the Artifact Registry before this date.
May 22, 2025: All requests to the gcr.io domain will be handled exclusively by Artifact Registry. Ensure the Artifact Registry API is enabled.

[ameukam]

/priority important-longterm

[ameukam]

cc @kubernetes/release-engineering

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[ameukam]

/remove-lifecycle stale