replace milind to yuedong for qe members

[huali9]

refer #31927, replace milind to yuedong as a secondary cherry pick approver. @sunzhaohua2 @lunarwhite PTAL, thanks.

liuhuali@Lius-MacBook-Pro release % make prow-config
false || docker pull --platform linux/amd64 quay.io/openshift/ci-public:ci_auto-config-brancher_latest
ci_auto-config-brancher_latest: Pulling from openshift/ci-public
1174ed37633c: Already exists 
1370def9c30e: Pull complete 
Digest: sha256:028ab448bed2947f8e474b68df192b6488dc0032096f76bf312934829c0b32da
Status: Downloaded newer image for quay.io/openshift/ci-public:ci_auto-config-brancher_latest
quay.io/openshift/ci-public:ci_auto-config-brancher_latest
docker run --platform linux/amd64 --user 501:20 --rm -v "/Users/liuhuali/project/release/core-services/prow/02_config:/config:z" --entrypoint=/usr/bin/determinize-prow-config quay.io/openshift/ci-public:ci_auto-config-brancher_latest --prow-config-dir /config --sharded-prow-config-base-dir /config --sharded-plugin-config-base-dir /config
liuhuali@Lius-MacBook-Pro release % 

[openshift-ci-robot]

[REHEARSALNOTIFIER]
@huali9: no rehearsable tests are affected by this change

Note: If this PR includes changes to step registry files (ci-operator/step-registry/) and you expected jobs to be found, try rebasing your PR onto the base branch. This helps pj-rehearse accurately detect changes when the base branch has moved forward.

[openshift-ci]

@huali9: all tests passed!

Full PR test history. Your PR dashboard.

Details

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.

[huali9]

/assign @damdo

[damdo]

/approve

Welcome!

[lunarwhite]

Thanks both!

I'm wondering if we can safely drop below section from each repo going forward, since cherry-pick-approved labeling restriction was included to support an old process

- allowed_users:
      - <QE member>
      assign_on:
      - label: backport-risk-assessed
      label: cherry-pick-approved

https://redhat-internal.slack.com/archives/GE2HQ9QP4/p1773910211759879

[JoelSpeed]

/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

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

Details

Needs approval from an approver in each of these files:

• core-services/prow/02_config/openshift/azure-service-operator/OWNERS [JoelSpeed,damdo]
• core-services/prow/02_config/openshift/cloud-provider-alibaba-cloud/OWNERS [JoelSpeed]
• core-services/prow/02_config/openshift/cloud-provider-aws/OWNERS [JoelSpeed,damdo]
• core-services/prow/02_config/openshift/cloud-provider-azure/OWNERS [JoelSpeed,damdo]
• core-services/prow/02_config/openshift/cloud-provider-gcp/OWNERS [JoelSpeed,damdo]
• core-services/prow/02_config/openshift/cloud-provider-ibm/OWNERS [JoelSpeed,damdo]
• core-services/prow/02_config/openshift/cloud-provider-nutanix/OWNERS [JoelSpeed,damdo]
• core-services/prow/02_config/openshift/cloud-provider-vpc-controller/OWNERS [JoelSpeed,damdo]
• core-services/prow/02_config/openshift/cloud-provider-vsphere/OWNERS [JoelSpeed,damdo]
• core-services/prow/02_config/openshift/cluster-api/OWNERS [JoelSpeed,damdo]
• core-services/prow/02_config/openshift/cluster-api-actuator-pkg/OWNERS [JoelSpeed,damdo,huali9]
• core-services/prow/02_config/openshift/cluster-api-operator/OWNERS [JoelSpeed,damdo]
• core-services/prow/02_config/openshift/cluster-api-provider-alibaba/OWNERS [JoelSpeed,damdo]
• core-services/prow/02_config/openshift/cluster-api-provider-aws/OWNERS [JoelSpeed,damdo]
• core-services/prow/02_config/openshift/cluster-api-provider-azure/OWNERS [JoelSpeed,damdo]
• core-services/prow/02_config/openshift/cluster-api-provider-gcp/OWNERS [JoelSpeed,damdo]
• core-services/prow/02_config/openshift/cluster-api-provider-ibmcloud/OWNERS [JoelSpeed,damdo]
• core-services/prow/02_config/openshift/cluster-api-provider-nutanix/OWNERS [JoelSpeed,damdo]
• core-services/prow/02_config/openshift/cluster-api-provider-openshift/OWNERS [JoelSpeed,damdo]
• core-services/prow/02_config/openshift/cluster-api-provider-vsphere/OWNERS [JoelSpeed,damdo]
• core-services/prow/02_config/openshift/cluster-autoscaler-operator/OWNERS [JoelSpeed,damdo]
• core-services/prow/02_config/openshift/cluster-capi-operator/OWNERS [JoelSpeed,damdo]
• core-services/prow/02_config/openshift/cluster-cloud-controller-manager-operator/OWNERS [JoelSpeed,damdo]
• core-services/prow/02_config/openshift/cluster-control-plane-machine-set-operator/OWNERS [JoelSpeed,damdo]
• core-services/prow/02_config/openshift/cluster-machine-approver/OWNERS [JoelSpeed,damdo]
• core-services/prow/02_config/openshift/kubernetes-autoscaler/OWNERS
• core-services/prow/02_config/openshift/machine-api-operator/OWNERS [JoelSpeed,damdo]
• core-services/prow/02_config/openshift/machine-api-provider-aws/OWNERS [JoelSpeed,damdo]
• core-services/prow/02_config/openshift/machine-api-provider-azure/OWNERS [JoelSpeed,damdo]
• core-services/prow/02_config/openshift/machine-api-provider-gcp/OWNERS [JoelSpeed,damdo]
• core-services/prow/02_config/openshift/machine-api-provider-ibmcloud/OWNERS [JoelSpeed,damdo]
• core-services/prow/02_config/openshift/machine-api-provider-nutanix/OWNERS [JoelSpeed,damdo]
• core-services/prow/02_config/openshift/machine-api-provider-powervs/OWNERS [JoelSpeed]

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

[damdo]

We need approval from @elmiko

too