Migrate to registry.k8s.io

[Babbili]

This PR fixes #34922

This PR migrates from gcr.io/k8s-testimages which is a legacy Google-owned GCR/AR deprecated repo to registry.k8s.io/ a Kubernetes community-owned.

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: Babbili / name: Babbili (5484226, cb938e7, dd2cbf0)

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: Babbili
Once this PR has been reviewed and has the lgtm label, please assign dims for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[k8s-ci-robot]

Welcome @Babbili!

It looks like this is your first PR to kubernetes/test-infra 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/test-infra has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @Babbili. Thanks for your PR.

I'm waiting for a github.com member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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-sigs/prow repository.

[Babbili]

also they're other changes for the same gcr.io/k8s-testimages maybe considered in other repositories (kubernetes/pref-tests, ...) , as in here

[BenTheElder]

Simple substitution like this does not work, this image does not exist.

Please confirm that these images exist.

[BenTheElder]

@cpanato it kinda looks like we could archive this repo and turn down the CI jobs, no commits since January 2022 ...

[Babbili]

you're right, i'd push the images that doesn't exist yet, please which project, artifact repo and region, i don't have access to the GCP projects, will i need a serviceaccount key instead or creating a prow job will do it. i found this maybe helpful

[BenTheElder]

This isn't an image we built, it was copied from launcher.gcr.io/google/bazel, we should avoid building yet another image ourselves, working with the owners of github.com/kubernetes/repo-infra to find a solution.

Perhaps the bazel parts of this repo can be deleted and this replaced with a kubekins-e2e job running make.

We do not have any humans pushing images directly. See https://github.com/kubernetes/registry.k8s.io?tab=readme-ov-file#registryk8sio

[BenTheElder]

this image does not exist.

[BenTheElder]

Many of our CI jobs use staging images, which is an exception to the general guidance to use production published images. These images are not published because they're not intended for external re-use, they're internal to the project.

However, this should point to the community owned project

[BenTheElder]

cc @kubernetes/sig-k8s-infra-leads