migrate to registry.k8s.io from gcr.io

[darshansreenivas]

This PR replaces usage of the legacy Google-owned gcr.io/k8s-testimages registry with the community-owned registry.k8s.io/k8s-testimages.

This change aligns with Kubernetes community guidelines to decouple from Google-owned infrastructure.

Ref: #1387

[k8s-ci-robot]

Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it.

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.

[k8s-ci-robot]

Hi @darshansreenivas. Thanks for your PR.

I'm waiting for a kubernetes-csi 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.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: darshansreenivas
Once this PR has been reviewed and has the lgtm label, please assign msau42 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

[darshansreenivas]

cc @xing-yang

[xing-yang]

/hold

[jsafrane]

/ok-to-test

Neither registry.k8s.io/distroless/static:latest nor registry.k8s.io/k8s-testimages/gcb-docker-gcloud:v20240718-5ef92b5c36 exist for me, I'm checking if CI can find them.

[k8s-ci-robot]

@darshansreenivas: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-kubernetes-csi-external-provisioner-1-33-on-kubernetes-1-33	64cd756	link	false	/test pull-kubernetes-csi-external-provisioner-1-33-on-kubernetes-1-33
pull-kubernetes-csi-external-provisioner-1-32-on-kubernetes-1-32	64cd756	link	true	/test pull-kubernetes-csi-external-provisioner-1-32-on-kubernetes-1-32
pull-kubernetes-csi-external-provisioner-distributed-on-kubernetes-1-26	64cd756	link	true	/test pull-kubernetes-csi-external-provisioner-distributed-on-kubernetes-1-26
pull-kubernetes-csi-external-provisioner-1-31-on-kubernetes-1-31	64cd756	link	true	/test pull-kubernetes-csi-external-provisioner-1-31-on-kubernetes-1-31
pull-kubernetes-csi-external-provisioner-unit	64cd756	link	true	/test pull-kubernetes-csi-external-provisioner-unit

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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. I understand the commands that are listed here.

[jsafrane]

#2 ERROR: registry.k8s.io/distroless/static:latest: not found