marathon-lb
marathon-lb copied to clipboard
zdd.py has issue with servicePort set to 0
currently if we set servicePort to 0 and pass it to zdd.py, servicePort will be replaced with a randomly assigned port vaule, however, HAPROXY_0_PORT in labels have value 0 instead of the randomly assigned value, which is incorrect;
this is observed in commit f52632d58a5e90b15aded62297d24f9bd4296023
Don't use 0; allocate a port.
Doesn't this restrict a service to one instance per Mesos slave when using HOST networking?