summaryrefslogtreecommitdiff
path: root/src/migration-scripts
diff options
context:
space:
mode:
authorch4nn0n <josh@channon.dev>2026-07-15 21:41:22 +0800
committerch4nn0n <josh@channon.dev>2026-10-03 14:51:35 +0800
commite18992ca19b64561e873957a4c2590487601f4f5 (patch)
tree0aefa8132bbf8aaf21fc16b263563d332f6087ff /src/migration-scripts
parent5c515753eafa43aceba3eb4dc03c6935cbf0fdb5 (diff)
downloadvyos-1x-e18992ca19b64561e873957a4c2590487601f4f5.tar.gz
vyos-1x-e18992ca19b64561e873957a4c2590487601f4f5.zip
haproxy: T9097: add ssl checks-only for TLS health checks
When load balancing TLS backends in TCP passthrough mode there is currently no way to perform an HTTPS health check: http-check sends the request in plaintext, and the only TLS option (backend ssl no-verify/ca-certificate) renders the 'ssl' keyword on the server lines, which re-encrypts the forwarded traffic and breaks passthrough of clients that already speak TLS end-to-end (e.g. kube-apiserver clients authenticating with TLS client certificates). Add 'set load-balancing haproxy backend <name> ssl checks-only' (valueless). When set, the existing backend ssl options apply to health checks only: server lines get 'check-ssl verify none' or 'check-ssl ca-file <ca>.pem' instead of 'ssl ...', leaving forwarded traffic untouched. Commit validation rejects checks-only when no server in the backend has check enabled, or when neither no-verify nor ca-certificate is set, since either case would otherwise be inert. Existing configurations render unchanged.
Diffstat (limited to 'src/migration-scripts')
0 files changed, 0 insertions, 0 deletions