Move the haproxy edge behind the external Traefik #492
Reference in New Issue
Block a user
Delete Branch "benvin/haproxy-behind-traefik"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The haproxy edge holds its own DMZ VIP, a second public entry point alongside
traefik-external that must be firewalled and DNS'd separately. Traefik can
front it with TLS passthrough, leaving haproxy's certs and backends untouched.
traefik-externalGateway: HTTP :80 plus Passthrough TLS :443.fe_https.maphostnames to haproxy:443; HTTPRoute 301s :80.fe_http,be_letsencryptandfe_http.map; certs are DNS-01 only.Client IP now reads as a Traefik pod — the Gateway provider cannot emit PROXY protocol to a TLSRoute backend.
sessionAffinitygoes too (it would pin Traefik pods, not clients); SRVNAME cookies keep persistence.