Hello.
I struggle with ssl-redirect issue described in #788
As a workaround I have such configuration in my helm value file:
## Custom configuration for Controller
## ref: https://github.com/haproxytech/kubernetes-ingress/tree/master/documentation
config:
# Disable build-in redirect to http as it add internal port to location block
# BUG: https://github.com/haproxytech/kubernetes-ingress/pull/788
ssl-redirect: "false"
ssl-redirect-code: "302"
frontend-config-snippet: |-
# Workaround for broken redirect, http -> https with exception for ACME challenge:
http-request redirect scheme https code 307 if !{ ssl_fc } !{ path_beg /.well-known/acme-challenge/ }
After helm upgrade I see in the logs:
2026/05/06 11:24:11 INFO controller/controller.go:227 [transactionID=add8054a-5c9d-4115-9794-af84c07a8151] HAProxy reloaded
2026/05/06 11:24:57 INFO store/events.go:303 configmap 'haproxy/haproxy-kubernetes-ingress' updated
But when I called my domain by using curl I got old http code from my snippet,
eg. I set now in the snippet to return code 307 but the curl return me the previous one, eg 303.
The config file is updated inside the pod.
I also tried
global-config-snippet: |-
hard-stop-after 10s
and
extraArgs:
- --disable-quic
- --sync-period=10s
but without success, the only way to load proper configuration is to full restart of haproxy pods.
Also notice some unstoppable Jobs in haproxy:
'echo "show info" | socat stdio /var/run/haproxy-runtime-api.sock' | grep -i "hard\|stop"
Hard_maxconn: 41000
Stopping: 0
Unstoppable Jobs: 1
This issue is critical as I'm not sure if the ingress configuration applied by the Ingress objects be the latest one used by haproxy controller.
Used chart: haproxytech/kubernetes-ingress version 1.49.0
Hello.
I struggle with ssl-redirect issue described in #788
As a workaround I have such configuration in my helm value file:
After helm upgrade I see in the logs:
But when I called my domain by using curl I got old http code from my snippet,
eg. I set now in the snippet to return code 307 but the curl return me the previous one, eg 303.
The config file is updated inside the pod.
I also tried
but without success, the only way to load proper configuration is to full restart of haproxy pods.
Also notice some unstoppable Jobs in haproxy:
This issue is critical as I'm not sure if the ingress configuration applied by the Ingress objects be the latest one used by haproxy controller.
Used chart: haproxytech/kubernetes-ingress version 1.49.0