tree 7855964d39eb8df2098a8863ebed872fd2c5ba9c
parent 03578a6e74d6a3ae240102b4bf5b61344d1f8fec
author Antonio Barone <syntonyze@gmail.com> 1603818961 +0100
committer Antonio Barone <syntonyze@gmail.com> 1603883588 +0000

Separate ha-proxy from masters

Not having a specific placement strategy for ha-proxy might cause them
to be deployed on the same ec2-instance as the masters.

If tasks are running on the same instance, both source and destination
IP are the same when being received by the target instance and this
causes packets to be dropped as per convention for L4 networking[1].

Ensure ha-proxies are never deployed to the same ec2-instance as the
masters by creating a dedicated ASG for them and forcing the placement
on ec2-instances labelled as 'haproxy'.

[1]https://aws.amazon.com/premiumsupport/knowledge-center/target-connection-fails-load-balancer/

Bug: Issue 13565
Change-Id: I38ad5d29db6bd61d8f0396fc1468b72be5c0adb7