[doc] Document usage of binding to interface

Code Issues Proposed changes

Change-Id: Iba1f4a284beaba8d2d7f020ca7ad2d78d6360161

This commit is contained in:

Dmitriy Rabotyagov

2023年07月26日 12:36:40 +02:00

committed by Dmitriy Rabotyagov

parent cb4eb8b327

commit 2d8fd9bfef

1 changed files with 18 additions and 0 deletions

@@ -339,6 +339,24 @@ This can be set in the ``user_variables.yml`` file:

haproxy_bind_external_lb_vip_address:10.0.0.10

haproxy_bind_internal_lb_vip_address:192.168.0.10

Binding haproxy to interface

~~~~~~~~~~~~~~~~~~~~~~~~~~~~

In some cases it might be more convenient to bind haproxy to the interface

rather then a specific IP address. For example, this is handy if you decide

to balance load between HAProxy instances using DNS RR, where each HAProxy

will have it's own VIP which will failover to others.

Binding to the interface can be set by providing following variables

in the ``user_variables.yml`` file:

.. code-block:: yaml

haproxy_bind_external_lb_vip_address:"*"

haproxy_bind_internal_lb_vip_address:"*"

haproxy_bind_external_lb_vip_interface:bond0

haproxy_bind_internal_lb_vip_interface:br-mgmt

Adding Access Control Lists to HAProxy front end

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~