[1.27] dependencies: update etcd dependencies to v3.5.9

[liangyuanpeng]

What type of PR is this?

/kind cleanup

What this PR does / why we need it:

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Hold on it if we need to waiting for the image references of etcd to v3.5.9: #118079

Does this PR introduce a user-facing change?

NONE

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

[k8s-ci-robot]

This cherry pick PR is for a release branch and has not yet been approved by Release Managers.
Adding the do-not-merge/cherry-pick-not-approved label.

To merge this cherry pick, it must first be approved (/lgtm + /approve) by the relevant OWNERS.

If you didn't cherry-pick this change to all supported release branches, please leave a comment describing why other cherry-picks are not needed to speed up the review process.

If you're not sure is it required to cherry-pick this change to all supported release branches, please consult the cherry-pick guidelines document.

AFTER it has been approved by code owners, please leave the following comment on a line by itself, with no leading whitespace: /cc kubernetes/release-managers

(This command will request a cherry pick review from Release Managers and should work for all GitHub users, whether they are members of the Kubernetes GitHub organization or not.)

For details on the patch release process and schedule, see the Patch Releases page.

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]

This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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]

Hi @liangyuanpeng. Thanks for your PR.

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

[alexzielenski]

/remove-sig api-machinery

[liangyuanpeng]

area/etcd

[liangyuanpeng]

/area etcd

[neolit123]

/remove-sig api-machinery
/sig etcd

[k8s-ci-robot]

@neolit123: Those labels are not set on the issue: sig/api-machinery

In response to this:

/remove-sig api-machinery
/sig etcd

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: liangyuanpeng
Once this PR has been reviewed and has the lgtm label, please assign liggitt, sttts 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
• staging/src/k8s.io/apiextensions-apiserver/OWNERS
• staging/src/k8s.io/apiserver/OWNERS
• staging/src/k8s.io/cloud-provider/OWNERS
• staging/src/k8s.io/controller-manager/OWNERS
• staging/src/k8s.io/kube-aggregator/OWNERS
• staging/src/k8s.io/kube-controller-manager/OWNERS
• staging/src/k8s.io/legacy-cloud-providers/OWNERS
• staging/src/k8s.io/pod-security-admission/OWNERS
• staging/src/k8s.io/sample-apiserver/OWNERS
• vendor/OWNERS

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

[liangyuanpeng]

/remove-sig api-machinery

[liangyuanpeng]

Sinces PR #118079 is merged, i think this PR is ready for review,Thanks.

/cc @neolit123 @serathius @ahrtr @wenjiaswe I hope i have cc correctly.

[pacoxu]

#117645 bumped to v3.5.9 for v1.28.

This seems to be a cherry-pick for #117645.

If you didn't cherry-pick this change to all supported release branches, please leave a comment describing why other cherry-picks are not needed to speed up the review process.

If you're not sure is it required to cherry-pick this change to all supported release branches, please consult the cherry-pick guidelines document.

Does this fix a special issue/bug in v1.27? If not, this may not fulfill the cherry-pick policy.

#118079 is merged as it will help to upgrade to the new etcd version to fix etcd bugs. For the dependencies bump, we should know what is fixed with this bump.

As I know, only some CVE related dependencies bump will be accepted like #120768.

[dashpole]

/remove-sig instrumentation

[logicalhan]

/sig etcd

[k8s-ci-robot]

PR needs rebase.

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.

[wenjiaswe]

/assign @serathius @siyuanfoundation

[pacoxu]

#121573 bumped the kube v1.29(current master) to etcd v3.5.10.