Hi
On 28.08.2016 19:57, Baptiste wrote:
> This should happen soon, for 1.7.
I noticed Willy's email “1.7 => almost there” and wanted to test out the
feature. Has this feature been implemented for 1.7? I noticed the
init-addr feature mentioned in the dev6 release announcement and
modified the configuration in my initial mail to the following:
server nginx1 nginx.containers.example.com:80 check resolvers
containers resolve-prefer ipv4 init-addr last,libc,none
server nginx2 nginx.containers.example.com:80 check resolvers
containers resolve-prefer ipv4 init-addr last,libc,none
server nginx3 nginx.containers.example.com:80 check resolvers
containers resolve-prefer ipv4 init-addr last,libc,none
server nginx4 nginx.containers.example.com:80 check resolvers
containers resolve-prefer ipv4 init-addr last,libc,none
haproxy started up without any A records at
nginx.containers.example.com, great! It also brought the backends down
once the record disappeared, also great!
Unfortunately it still sent the requests to a single nginx backend only,
instead of using all the available IP addresses.
Did I configure something wrong?
Best regards
Tim Düsterhus
