Yan Bondarenko 12cc48d465 fix(tcp-balancer): rename backends and pin HAProxy so the chart starts on 3.3+ ...

haproxy:latest now resolves to 3.3 and newer, where a backend named like
a frontend is a fatal config error, so every tcp-balancer pod fails at
config parse. Backends get a _backend suffix and the image follows the
chart appVersion on the 3.4 LTS line instead of a floating tag.

The whitelist rules render inside one guard. On the kubernetes and talos
frontends an empty whitelist means no filtering; whitelistHTTP with an
empty whitelist fails the render, because a security opt-in that quietly
became a no-op would not be noticed the way a crash is.

The unittest suite pins the rendered config for the default, whitelist
and failure cases and the image pin, so a template refactor cannot bring
the collision or the floating tag back.

Fixes #1966

Signed-off-by: Yan Bondarenko <202671653+yankawai@users.noreply.github.com>

2026-09-23 11:18:19 +04:00

..

apps

fix(tcp-balancer): rename backends and pin HAProxy so the chart starts on 3.3+

2026-09-23 11:18:19 +04:00

core

feat(talos-log-collector): add talos-log-collector package (#3260)

2026-09-22 23:49:33 +04:00

extra

fix(keycloak): complete realm-name coverage and guard non-string names

2026-09-21 12:15:10 +03:00

library

fix(backups): give the sidecar sizing its reason per caller

2026-09-18 17:30:20 +04:00

system

feat(kube-ovn): bump kube-ovn to v1.15.26 (#4331)

2026-09-23 02:42:25 +04:00

tests/cozy-lib-tests

fix(cozy-lib): guard fractional-negative minReplicaCount and cover the pause-merge collision

2026-09-10 15:31:24 +03:00