Closed mauilion closed 4 years ago
dlipovetsky
commented
5 years ago Thanks @mauilion!
Today, etcdadm uses the IP address associated with the host's default interface to derive the advertise/listen peer and client URL. I agree, etcdadm should allow the user to specify an IP address.
(This assumes that the user-specified IP would be used to derive both peer and client URLs. Have you seen cases where the peer and client traffic needs to go to different IPs?)
mauilion
commented
5 years ago I've not. I've seen many cases where advertise and listen addresses are different.
Listen address sets the IP the etcd will bind to and must be an ip or 0.0.0.0 Advertise is the ip or fqdn that peers or clients will use to address the etcd node. It can be an ip or an fqdn. More important when configuring TLS.
dlipovetsky
commented
5 years ago Got it. Then etcdadm should allow the user to specify the listen and advertise addresses.
fejta-bot
commented
5 years ago Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle stale
fejta-bot
commented
5 years ago Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle rotten
pytimer
commented
4 years ago @dlipovetsky What's progress for this feature, can you tell me, thanks? Now I have user case that one host have multi network interface, one of external address and others are internal address, i need etcd bind one of internal address, this internal address maybe not the default interface.
fejta-bot
commented
4 years ago Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle stale
fejta-bot
commented
4 years ago Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle rotten
fejta-bot
commented
4 years ago Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle stale
fejta-bot
commented
4 years ago Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle rotten
fejta-bot
commented
4 years ago Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /close
k8s-ci-robot
commented
4 years ago @fejta-bot: Closing this issue.
Uzibird
commented
1 year ago still　mention me that : unknown flag: --listen-address
etcd version (default "3.3.8")
is my etcd version wrong?
This is necessary for environments like Vagrant that have multiple network interfaces.
if I could specify the ip that is used to resolve the external address this would solve this.