Change etcd-events listen port to avoid conflicts

[zhengtianbao]

What type of PR is this?

/kind bug

What this PR does / why we need it:

There is a confilct of etcd_metrics_port and etcd-events listen_client_port, both of them are 2381.

Which issue(s) this PR fixes:

Fixes #8230

Does this PR introduce a user-facing change?:

Change etcd-events listen port (2381 -> 2383) to avoid conflicts

[k8s-ci-robot]

Hi @zhengtianbao. Thanks for your PR.

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

[floryut]

@zhengtianbao Thank you for the PR 👍
/ok-to-test

[floryut]

@zhengtianbao Sorry but you need to rebase master, otherwise CI won't work

[zhengtianbao]

ok， I'm outside this weekend, I will do it next week🙏

[khatrig]

@zhengtianbao , Couple of points on defining separate etcd-events cluster.

• Currently, etcd_metrics_port defaults to 2381, etcd-events will need a separate default port(and a new variable eg. etcd_events_metrics_port default -2383?) to avoid conflicts.
• etcd-events.env template doesn't have a metrics port defined yet, I'm not sure if etcd-events will support metrics this way.

[zhengtianbao]

@zhengtianbao , Couple of points on defining separate etcd-events cluster.

• Currently, etcd_metrics_port defaults to 2381, etcd-events will need a separate default port(and a new variable eg. etcd_events_metrics_port default -2383?) to avoid conflicts.
• etcd-events.env template doesn't have a metrics port defined yet, I'm not sure if etcd-events will support metrics this way.

Thanks for your advice, I think whether etcd-events metrics is supported or not needs to be discussed. If we do need it, then I will submit another PR to implement it.

[cristicalin]

Looks good. Thank you @zhengtianbao for this change!

/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cristicalin, floryut, zhengtianbao

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:

• OWNERS [floryut]

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