We have the same use case as Alex *(mesos load balancing), and also confirm that our config worked without change 1.6->1.8.
Given our testing you should consider the seamless reload -x option, and the dynamic server configuration apis. Both have greatly alleviated issues we've faced in our microservices-based cloud. Dave. On Mon, Jul 16, 2018 at 8:47 AM Alex Evonosky <alex.evono...@gmail.com> wrote: > Tim- > > I can speak from a production point of view that we had HAproxy on the 1.6 > branch inside docker containers for mesos load balancing with pretty much > the same requirements as you spoke of. After compiling Haproxy to the 1.8x > branch the same config worked without issues. > > -Alex > > > On Mon, Jul 16, 2018 at 9:39 AM, Tim Verhoeven <tim.verhoeven...@gmail.com > > wrote: > >> Hello all, >> >> We have been running the 1.6 branch of HAProxy, without any issues, for a >> while now. And reading the updates around 1.8 here in the mailing list it >> looks like its time to upgrade to this branch. >> >> So I was wondering if there are any things I need to look of for when >> doing this upgrade? We are not doing anything special with HAProxy (I >> think). We run it as a single process, we use SSL/TLS termination, some >> ACL's and a bunch of backends. We only use HTTP 1.1 and TCP connections. >> >> From what I've been able to gather my current config will works just as >> good with 1.8. But some extra input from all the experts here is always >> appreciated. >> >> Thanks, >> Tim >> > >