Can we get the ability to configure the peer namespace?
Right now haproxy uses the default namespace, but in our system we have
an "internal" interface which is able to talk to the other haproxy
nodes, and this interface is in another network namespace.

Additionally, the error output for failure to bind to a peer address is
lacking. I had to do an `strace` to figure out what the error was:
[ALERT] 282/214021 (2725) : [haproxy.main()] .
[ALERT] 282/214021 (2725) : [haproxy.main()] Some protocols failed to
start their listeners! Exiting.

That's on haproxy 1.6.9

Anyway, I can change the namespace that haproxy is launched in, and then
manually override the namespace for every `bind` and `server` parameter,
but it's rather cumbersome to do so. Would be much nicer to be able to
control the peer binding namespace, just like any other bind.

If this would be a simple change, I might be willing to attempt it. But
I've never worked in the haproxy source before, so not sure how involved
it would be.

Thanks

-Patrick

Reply via email to