Consul: How should I use one ip to access the consul cluster.
How should I use one ip to access a consul cluster. For example there is 3 nodes consul cluster
consul node 1 : 10.10.10.2:8500 leader
consul node 2 : 10.10.10.3:8500 follow
consul node 3 : 10.10.10.4:8500 follow
How should I use one ip + port to access the consul cluster without inviting other software like nginx?
Silence2012
All 9 comments
Any type of load balancer, such as haproxy, nginx, f5, etc, or even just as simple as a VIP, setup with keepalived. Consul UI is treated like any other web service for that purpose.
jfgibbins
on 18 Sep 2017
You should not put consul behind a load balancer but instead install a local agent on all of your nodes and then connect to localhost:8500. The requests will be automatically forwarded to the current leader.
magiconair
on 20 Sep 2017
@magiconair Yes, that would be true for applications that are using consul, but you certainly wouldn't install it on your local pc to access for management, so yes, there is reason to want to have it behind a cluster ip. Unfortunately consul does not handle VIP on its own, so if you want to access it from a non-agent machine, the servers would need to be put behind a lb or vip. I personally run it on top of docker swarm, which handles it using the ingress network, but that requires some adjustments, as consul's method of storing server IPs in raft, is rather crippling.
jfgibbins
on 20 Sep 2017
@jfgibbins Did you have some tricks about this?
Saliva520319
on 10 Nov 2017
The best way to deal with the PC use case is probably via DNS (configure a DNS name with the Consul servers, for example) or some kind of LB or proxy, but for all other use cases we definitely recommend running the agent. Hope that helps!
slackpad
on 20 Dec 2017
any LB or proxy suggestion?@slackpad
Jaware
on 20 Dec 2017
@Jaware Hello, have you solved this problem?
How do you connect to the consul cluster now, Did you use the LB or proxy ?
BealChen
on 15 Nov 2018
One option is to use DNS forwarding in the local network. You can then point your browser at http(s)://consul.service.[dc].consul/
ferrix
on 28 Nov 2018
write little lb code yourself, just a for loop
Jaware
on 19 Jan 2019
Related issues
wargamez
路
4Comments
powerman
路
3Comments
atomantic
路
4Comments
wing731
路
3Comments
hooksie1
路
3Comments
Most helpful comment
@magiconair Yes, that would be true for applications that are using consul, but you certainly wouldn't install it on your local pc to access for management, so yes, there is reason to want to have it behind a cluster ip. Unfortunately consul does not handle VIP on its own, so if you want to access it from a non-agent machine, the servers would need to be put behind a lb or vip. I personally run it on top of docker swarm, which handles it using the ingress network, but that requires some adjustments, as consul's method of storing server IPs in raft, is rather crippling.