[3.5] Support multiple values for allowed client and peer TLS identities

[lhy1024]

Please read https://github.com/etcd-io/etcd/blob/main/CONTRIBUTING.md#contribution-flow.
cherry pick #18015 to release-3.5

[k8s-ci-robot]

Hi @lhy1024. Thanks for your PR.

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

[ivanvc]

Thanks for your PR, @lhy1024. Please take a look at my comments. I suggest adding the original commit and PR to your commit message so it's easier to trace where this backport comes from later.

[ivanvc]

/ok-to-test

[ivanvc]

From a backporting point of view, this looks correct. Thanks, @lhy1024.
cc. @ahrtr, @serathius.

[lhy1024]

PTAL @serathius @jmhbnz

[lhy1024]

Could you please let me know when this PR might be merged? @ivanvc @ahrtr

[jmhbnz]

LGTM - Thanks for your efforts on this @lhy1024

I initially held off adding a review to this pull request as it's a feature, which ordinarily we would try to avoid backporting. However, given:

• Our next minor release is still distant
• Feature is minor in terms of impact to codebase
• Tests have been written and included in backport
• Community has asked for this and provided clear use case

I think it is best if we proceed with the backport and include it in etcd v3.5.15

[lhy1024]

LGTM - Thanks for your efforts on this @lhy1024

I initially held off adding a review to this pull request as it's a feature, which ordinarily we would try to avoid backporting. However, given:

• Our next minor release is still distant
• Feature is minor in terms of impact to codebase
• Tests have been written and included in backport
• Community has asked for this and provided clear use case

I think it is best if we proceed with the backport and include it in etcd v3.5.15

Thank you for your review, could you please tell me when etcd v3.5.15 will be released? Whether do I need to add change log in new PR?

[ahrtr]

could you please tell me when etcd v3.5.15 will be released?

Please read https://github.com/etcd-io/etcd/blob/main/Documentation/contributor-guide/release.md#patch-release-criteria

Whether do I need to add change log in new PR?

Yes, please update https://github.com/etcd-io/etcd/blob/main/CHANGELOG/CHANGELOG-3.5.md#v3515-tbd

[lhy1024]

could you please tell me when etcd v3.5.15 will be released?

Please read https://github.com/etcd-io/etcd/blob/main/Documentation/contributor-guide/release.md#patch-release-criteria

Whether do I need to add change log in new PR?

Yes, please update https://github.com/etcd-io/etcd/blob/main/CHANGELOG/CHANGELOG-3.5.md#v3515-tbd

PTAL #18219 cc @ahrtr @jmhbnz