Join GitHub today
addvertise-wan only for inter-server communication? #1552
from my compose stack: https://github.com/ChristianKniep/orchestra/tree/master/consul-ambassador
I turns out that the
To fake some not-yet consularised services I would like to set-up a (some-what) 'hidden' DC that exposes services which are addvertised under the IP of the external service.
For starters 'Because I can', but on a more serious note - I want to containerise (and consulerise) a stack iteratively - one service at a time.
Until I haven't containerised
But if I could mock a hidden DC, which - once queried - exposes the IP of the external service, I could trick myself into heaven. :)
I would just have to specify
We got two networks: [EDIT: If you do not have a docker-network ready cluster, scroll down - down there I use
We got three internal consul agents:
First I start the internal server and attach the internal network afterwards:
The container now has two network interfaces:
Now start the rest:
Ping int0 (within the
I created an image with the patched version.
For some reason my version does not pick up the new configuration option
I changed the consul-ambassador stack to use the image:
And replayed the test, this time on a single-node (using
Error see above... :(
Missed, since the option was not picked up...
Now I'll try to ping
An node hiden within the
Build like this fails, that's why I use
I'm no expert, but if I had to guess, it could be due to different project path and GOPATH...? The package names shouldn't be prefixed with
I updated all my dependencies and built again cleanly, just to be sure
Nope, same error with 1.5:
OK, my bad - I didn't quite obey the GOPATH stuff... :) Now I got it...
It works! dancing
Pinging int2 from ext0 uses the WAN address of the client. :)
But that's a thing of the DNS server, thus of the agent of the host (container) which wants to reach out.
Anyway - that's fine to me. I'll write up a blog post and publish it here: http://qnib.org