tcp-balancer: HAProxy 3.3 breaks due to frontend/backend name collision

[lllamnyp]

Problem

The tcp-balancer app fails to start after HAProxy was updated to version 3.3. The app uses haproxy:latest which now pulls a version that no longer supports having frontend and backend with identical names.

Error Message

[ALERT]    (8) : config : Parsing [/usr/local/etc/haproxy/haproxy.cfg:18]: backend 'http' has the same name as frontend 'http' declared at /usr/local/etc/haproxy/haproxy.cfg:12. This is no longer supported as of 3.3. Please rename one or the other.

Root Cause

The configmap template in packages/apps/tcp-balancer/templates/configmap.yaml creates frontend/backend pairs with matching names:

• frontend http / backend http
• frontend https / backend https
• frontend kubernetes / backend kubernetes
• frontend talos / backend talos

This was valid in HAProxy < 3.3 but is now a breaking error.

Suggested Fix

1. Rename backends to use a suffix (e.g., backend http_backend, backend https_backend, etc.)
2. Pin the image version to avoid unexpected breakage from :latest (e.g., haproxy:2.9 or haproxy:3.2)

Option 2 is recommended as a best practice regardless—using :latest in production workloads can lead to unexpected breakage like this.

Affected Files

• packages/apps/tcp-balancer/templates/configmap.yaml - HAProxy config template
• packages/apps/tcp-balancer/templates/deployment.yaml - Image reference (haproxy:latest)

[dosubot]

The tcp-balancer app fails with HAProxy 3.3 because the config template defines frontend/backend pairs with identical names (like frontend http / backend http), which is no longer allowed in HAProxy 3.3+ and causes a startup error. The relevant config is in packages/apps/tcp-balancer/templates/configmap.yaml and the image is set to haproxy:latest in deployment.yaml, so the latest (breaking) version is always pulled.

To fix this, rename each backend to use a unique name (for example, backend http_backend instead of backend http) in the configmap template, and update the corresponding default_backend references in the frontend sections. Also, pin the HAProxy image in the deployment template to a known working version (such as haproxy:2.9 or haproxy:3.2) instead of using :latest to avoid future unexpected breakage. This approach is supported by both the code and a relevant GitHub issue discussing explicit version pinning for HAProxy in managed apps like tcp-balancer (source, config example, deployment example).

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}