Closed sashkachan closed 3 years ago
Why is it not configurable to change the consul endpoint? Possibly i'm missing something in how this is suppose to work but it seems the way it runs right now every single docker contianer needs to run consul which seems needlessly excessive.
I was confused about this also? Is the assumption the Mesos server itself is running consul? Seems pretty safe to add this patch
Due to the design on Consul, every mesos agent needs to run consul. mesos-consul connects to a consul instance that is running on the same node as the service is running on. Specifying a central consul endpoint will result in services being registered on that endpoint instead of on the mesos agent as they should be.
So I installed consul agent on all my mesos nodes, however it appears this code tries to access consul agent on a public interface not on 127.0.0.1, so it won't find it. As we dont want that exposed on the network.
+1
:+1:
+1
when it will be merged?
@sjkyspa When the build completes successfully. 👍
It also needs to be rebased to master first.
If you specify a consul agent, then all of the registered services will be assigned to that agent. So if you have a process running on say, mesos-worker-1, and register the service on consul-master-1, if consul-master-1 becomes unavailable then the service running on mesos-worker-1 goes critical. Which is clearly incorrect. I have specifically not merged this for that reason.
Adds address option to consul.