Replace deprecated k8s registry references

[jmhbnz]

Problem: Previously all of Kubernetes' image hosting has been out of gcr.io. There were significant egress costs associated with this when images were pulled from entities outside gcp. Refer to https://github.com/kubernetes/k8s.io/wiki/New-Registry-url-for-Kubernetes-(registry.k8s.io)

Solution: As highlighted at KubeCon NA 2022 k8s infra SIG update, the replacement for k8s.gcr.io which is registry.k8s.io is now ready for mainstream use and the old k8s.gcr.io has been formally deprecated and projects are requested to migrate off it. This pull request migrates remaining references for kubernetes-sigs/kustomize to registry.k8s.io.

[k8s-ci-robot]

Welcome @jmhbnz!

It looks like this is your first PR to kubernetes-sigs/kustomize 🎉. 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-sigs/kustomize 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 @jmhbnz. Thanks for your PR.

I'm waiting for a kubernetes-sigs 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/test-infra repository.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: jmhbnz
Once this PR has been reviewed and has the lgtm label, please assign natasha41575 for approval. For more information see the Kubernetes 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

[natasha41575]

/ok-to-test

[natasha41575]

@annasong20 Can you take a look at this and also some of the background that @jmhbnz put in the PR description? I'm aware that we need to migrate but I'm not sure of all the details

@jmhbnz Could you take a look at the test failures? Some of them appear to be potentially minor spacing issues. The error in the Lint test is unrelated to this PR and should be fixed soon.

[jmhbnz]

@jmhbnz Could you take a look at the test failures? Some of them appear to be potentially minor spacing issues. The error in the Lint test is unrelated to this PR and should be fixed soon.

Sorted, tests now passing - thanks @natasha41575.

[KnVerey]

Looks like we received duplicate PRs for this, and the other one merged last week: #5077

/close
/triage duplicate

[k8s-ci-robot]

@KnVerey: Closed this PR.

In response to this:

Looks like we received duplicate PRs for this, and the other one merged last week: #5077

/close
/triage duplicate

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.