Image promotion for cloud-provider-gcp v34.2.0

[linpu01]

Image promotion for cloud-provider-gcp v34.2.0
This is an automated PR generated from kpromo

kpromo pr --fork linpu01 --project cloud-provider-gcp --tag v34.2.0

/hold
cc: @kubernetes/release-engineering

[k8s-ci-robot]

Welcome @linpu01!

It looks like this is your first PR to kubernetes/k8s.io 🎉. 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/k8s.io 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 @linpu01. 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.

[YifeiZhuang]

It looks there are different ways of generating the images. That is why there are format is different.
@mattcary let us know if kpromo is still valid way of promoting the image. If not, what is the preferred way.
/lgtm
/assign @mattcary
cc. @upodroid

[upodroid]

Hey, this shell script was ran to generate the images: https://github.com/kubernetes/k8s.io/blob/main/registry.k8s.io/images/k8s-staging-cloud-provider-gcp/generate.sh. The yaml format is different, but the generated result is the same.

In the future, we should delete this script and use kpromo/manual diffs to promote the image.

This diff is safe to merge:

 mahamed  Mac  tmp  1  ERROR  $  curl -Lo new.yaml https://github.com/linpu01/k8s.io/53be90e6a08f929c3858561f0c9a0f152bc227fe/registry.k8s.io/images/k8s-staging-cloud-provider-gcp/images.yaml
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 26801  100 26801    0     0  66363      0 --:--:-- --:--:-- --:--:-- 66503
 mahamed  Mac  tmp  1  $  curl -Lo old.yaml https://github.com/kubernetes/k8s.io/refs/heads/main/registry.k8s.io/images/k8s-staging-cloud-provider-gcp/images.yaml
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 27296  100 27296    0     0  94618      0 --:--:-- --:--:-- --:--:-- 94777
 mahamed  Mac  tmp  1  $  diff <(yq -P 'sort_by(.name)' -o=props new.yaml) <(yq -P 'sort_by(.name)' -o=props old.yaml)
15d14
< 0.dmap.sha256\:4795f50bd273894d46e21b5569a716374377ae06d276343a6e5eae5aa93d5de8.0 = v34.2.0

[YifeiZhuang]

/assign saad-ali
/assign leiyiz

[upodroid]

LGTM

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: linpu01, upodroid

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:

• registry.k8s.io/images/k8s-staging-cloud-provider-gcp/OWNERS [upodroid]

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

[linpu01]

/unhold