+1 to the idea. Using service ports becomes unmanageable when there are
multiple products with lots of ports exposed.
AFAIU Udara has a point as well. The routing inside mesos-marathon
framework will work seamlessly with this. However to access it from the
outside (browser, etc.), we would need
Hi,
Container to contianer communication can be done by this as long as we run
a dns server.
However when users/browser wants to access a service running on a container
(say ESB maagement console) don't they have to come via marathon lb? Or
else do the they have to add our dns server to their
Hi,
Currently we are using Marathon-LB hostname and service ports in product
configuration when deploying on DC/OS (Apache Mesos). We can set the
--dns-search and --dns properties and set a DOMAIN and DNS server in
/etc/resolve.conf to resolve hostnames which are not found in /etc/hosts
[1].
