Move the haproxy edge behind the external Traefik (#492)

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.

- Add a `traefik-external` Gateway: HTTP :80 plus Passthrough TLS :443.
- TLSRoute the 12 `fe_https.map` hostnames to haproxy:443; HTTPRoute 301s :80.
- Make the Service ClusterIP on 443 only, releasing 198.18.199.1.
- Drop `fe_http`, `be_letsencrypt` and `fe_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. `sessionAffinity` goes too (it would pin Traefik pods, not clients); SRVNAME cookies keep persistence.

Reviewed-on: #492
Co-authored-by: unkin-agent <unkin-agent@unkin.net>
Co-committed-by: unkin-agent <unkin-agent@unkin.net>

apps/base/haproxy/service.yaml

@@ -4,23 +4,15 @@ kind: Service
 metadata:
   name: haproxy
   namespace: haproxy
-  annotations:
-    purelb.io/service-group: dmz
-    purelb.io/addresses: 198.18.199.1
 spec:
-  type: LoadBalancer
-  loadBalancerIP: "198.18.199.1"
-  # Source IP must survive for X-Real-IP.
-  externalTrafficPolicy: Local
-  # Pins a client to one replica, standing in for the dropped stick-table peers.
-  sessionAffinity: ClientIP
+  type: ClusterIP
+  # Reached only by the external Traefik's TLS-passthrough TLSRoute, so the
+  # peer address here is a Traefik pod, not the client. sessionAffinity is
+  # deliberately absent: keyed on ClientIP it would pin whole Traefik pods,
+  # not clients. Backend persistence rests on the per-backend SRVNAME cookie.
   selector:
     app: haproxy
   ports:
-    - name: http
-      port: 80
-      protocol: TCP
-      targetPort: http
     - name: https
       port: 443
       protocol: TCP