901523ddbb
In some user scenarious (like implementing DNS RR) it might be useful to bind on 0.0.0.0 but at the same time do not conflict with other services that are binded to the same ports. For that, we can specify a specific interface, on which haproxy will be binded to 0.0.0.0. In netstat it would be represented like `0.0.0.0%br-mgmt:5000`. With that we also allow to fully override `vip_binds` if assumtions that role make are not valid for some reason. Change-Id: Ic4c58ef53abc5f454b6fbebbd87292a932d173ae
13 lines
510 B
YAML
13 lines
510 B
YAML
---
|
|
|
|
features:
|
|
- |
|
|
Added variables ``haproxy_bind_external_lb_vip_interface`` and
|
|
``haproxy_bind_internal_lb_vip_interface`` that allows deployer to bind
|
|
haproxy on the specific interface only.
|
|
- |
|
|
Added variable ``haproxy_tls_vip_binds`` that allows to fully override
|
|
haproxy bindings, that are generated by the role if some assumptions are
|
|
not valid for some scenarios. It is list of mappings, that include address
|
|
and interface. Interface key is optional and can be ommited.
|