tripleo-heat-templates/deployment/haproxy
Damien Ciabrini c354d21131 Use frontend/backend sections in HAProxy config
Now that HAProxy configurations can leverage
frontend/backend statements [1], make this the new default
for this cycle, as it allows more complex proxying
scenario that are a prerequisite for optimizing the routing
of API calls in a HA control plane.

[1] Ieb36f90c6709934aa3aa6668d3929bff872c30f5

Change-Id: Ic25c258895872210e7cf2d760769b492842f0048
Related-Bug: #1941617
2021-10-01 09:30:17 +02:00
..
haproxy-container-puppet.yaml Use frontend/backend sections in HAProxy config 2021-10-01 09:30:17 +02:00
haproxy-edge-container-puppet.yaml Remove zaqar 2021-09-16 15:12:29 -06:00
haproxy-internal-tls-certmonger.j2.yaml Use server side env merging for ServiceNetMap/VipSubnetMap 2021-05-19 10:16:58 +05:30
haproxy-pacemaker-puppet.yaml Use server side env merging for ServiceNetMap/VipSubnetMap 2021-05-19 10:16:58 +05:30
haproxy-public-tls-certmonger.yaml Use server side env merging for ServiceNetMap/VipSubnetMap 2021-05-19 10:16:58 +05:30
haproxy-public-tls-inject.yaml Fix the failure condition for HAproxy chgrp script 2021-09-01 16:05:45 +00:00