Consul setup for a core DC and a few remote nodes
Hi there,
I'm looking at deploying Consul, initially only for basic service discovery to use with prometheus, and later for backend service config.
I have around 30 servers in one (core) site, which all share a public and a private network (but some of those don't have a public IP) , and around 10 more servers, where each of those is in some remote site. On the remote sites, I "own" only the remote server, which sits in a dedicated /30 IPv4 network, and don't have access to anything else.
From what I've read in Consul docs, it seems like I'll have to run a single-node Consul cluster on each of those remote nodes and then join them back to the core DC server instances using the WAN gossip pool.
Is this the correct way to do it, or am I over-complicating things?
Thanks for any info :)
Posted Sep 23, 2019, 1:45 PM UTC
If you only own one box and latency is low then I would advise running a cluster on your core and running a client on the remote. If connectivity to the remote to the core is severed then it ceases to be able to report its status or receive k/v updates. My 2 cents.
Yeah, this occured to me yesterday, since I basically just need a place to register services, I'll run just the 3-server cluster in the core, and then can use Ansible to fill the service catalog.
Thanks for the 2nd reassuring opinion :)