switch ci-kubernetes-e2e-ubuntu-gce-containerd to use new registry

[dims]

https://testgrid.k8s.io/google-gce#pull-kubernetes-e2e-gce-ubuntu-containerd&width=20 seems to be doing fine with preset-use-new-registry (set in #25608)

So let's add a bit more here. Switch the corresponding CI job to the new registry endpoint too

Signed-off-by: Davanum Srinivas [email protected]

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dims

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

The pull request process is described here

Needs approval from an approver in each of these files:

• config/jobs/kubernetes/sig-cloud-provider/OWNERS [dims]

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

[aojea]

/lgtm

[dims]

Ref: kubernetes/k8s.io#3411

[ameukam]

/lgtm

[ameukam]

/test pull-test-infra-prow-checkconfig

[ameukam]

/test pull-test-infra-prow-checkconfig
/check-cla

[dims]

/easycla

[dims]

/test pull-test-infra-unit-test

[k8s-ci-robot]

@dims: Updated the job-config configmap in namespace default at cluster test-infra-trusted using the following files:

• key gcp-gce.yaml using file config/jobs/kubernetes/sig-cloud-provider/gcp/gcp-gce.yaml

In response to this:

https://testgrid.k8s.io/google-gce#pull-kubernetes-e2e-gce-ubuntu-containerd&width=20 seems to be doing fine with preset-use-new-registry (set in #25608)

So let's add a bit more here. Switch the corresponding CI job to the new registry endpoint too

Signed-off-by: Davanum Srinivas [email protected]

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.