Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Support different advertise address for WAN gossip #527

Closed
brycekahle opened this issue Dec 9, 2014 · 12 comments
Closed

Support different advertise address for WAN gossip #527

brycekahle opened this issue Dec 9, 2014 · 12 comments

Comments

@brycekahle
Copy link

I would like the ability to use a node's public ip address for WAN gossip protocol, but retain use of the private ip for LAN gossip. This would negate the need to run a VPN tunnel between two datacenters.
@armon
Copy link
Member

armon commented Dec 10, 2014

Makes sense! Thanks!

@CheatCodes
Copy link

+1

3 similar comments
@dave-tucker
Copy link
Contributor

👍

@mavenugo
Copy link

👍

@arenstar
Copy link

+1

@dave-tucker dave-tucker mentioned this issue Feb 1, 2015
Merged
@bmonkman
Copy link

👍 Really need this.

@blalor
Copy link
Contributor

blalor commented Feb 20, 2015

Looking into joining clusters across disparate cloud providers and data centers. In some cases creating a vpn between these networks may not be advisable or possible, such as for regulatory reasons. Having separate advertise addresses for lan and wan pools is a must.

@fabx
Copy link

fabx commented Mar 10, 2015

+1

@pepov
Copy link

pepov commented Mar 21, 2015

+1 is there any progress on this already?

@pepov
Copy link

pepov commented Mar 25, 2015

As far as I can see the rpc advertise address should be separated too. I've managed to make the WAN gossip use a different address with this patch: pepov@9c3ef28

I suppose RPCAdvertise should be separated too for wan and lan. Is this a right way to go?

@pepov
Copy link

pepov commented Mar 25, 2015

Ok, I think I just overcomplicated this and there is no need to separate the rpc advertise address because it's only for the raft protocol. (Except when you want to config the raft layer different from what advertise_addr is set to)

@pepov pepov mentioned this issue Mar 25, 2015
Merged
@armon
Copy link
Member

armon commented May 7, 2015

Fixed in #816

@armon armon closed this as completed May 7, 2015
duckhan pushed a commit to duckhan/consul that referenced this issue Oct 24, 2021
@ishustava
Don't register duplicate services from different k8s namespaces (hash…
46cdc34 
…icorp#527)

When Consul namespaces are not enabled and we are processing a service
that already exists in Consul but with a different k8s namespace meta,
we skip service registration to avoid service name collisions.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
10 participants
@bmonkman @blalor @armon @arenstar @pepov @brycekahle @dave-tucker @fabx @CheatCodes @mavenugo