Kevin Fenzi 52a8936914 proxies: rework reversepassproxy and mark all ocp4 / ocp3 apps ...

The ocp3 cluster is reachable/available via the vpn, so any proxy can
reach it.

The ocp4 cluster is (at least for now) only reachable/available from the
iad2 proxies (proxy01/proxy10).

There's a firefox bug that causes it to reuse h2 connections, and in
some cases try and request something of a non iad2 proxy that it can't
reach. To work around this in those cases we need to send a 421 back to
the client so it doesn't do that.

This moves that logic into the template so all ocp4: true hosts do this
by default. Also, we default the balancer nodes so we only have to
change them in one place if we remove/add a compute node.

Finally, we mark all the ocp3 apps with 'ocp4: false' so we know what
they are and can move them more easily.

Signed-off-by: Kevin Fenzi <kevin@scrye.com>

2022-06-03 13:14:28 -07:00

..

main.yml

proxies: rework reversepassproxy and mark all ocp4 / ocp3 apps

2022-06-03 13:14:28 -07:00