Stop advertising GCR images, use registry.k8s.io or similar

[BenTheElder]

As discussed previously in https://github.com/kubernetes/test-infra/issues/31728#issuecomment-2025662460

A) GCR is deprecated B) Serving from a single region registry like this is not cost efficient. Originally it was only internal consumption by the project's own CI deployment.

If we want to publish images for external users it should really be at https://registry.k8s.io/ (note: images must go through image promotion, you cannot direct push), for internal usage it could be moved to an AR.

Prow at minimum will have to go through https://github.com/kubernetes/k8s.io/issues/1343 but will be special because other affected projects (at least as far as we know) serve users through registry.k8s.io already so the migration is less pressing ...

Really, we should be promoting images, along with tagging releases, now that we have a repo dedicated to prow.

/kind bug /priority important-soon

[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

[BenTheElder]

/lifecycle frozen