You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
k8s nodes routes loadbalancer traffic locally. if the listener is configured with PROXY protocol, the local traffic becomes unusable since haproxy requires the PROXY header.
What are you trying to do
k8s nodes routes loadbalancer traffic locally. if the listener is configured with PROXY protocol, the local traffic becomes unusable since haproxy requires the PROXY header.
See the k8s issue: kubernetes/kubernetes#66607
What HAProxy Ingress should do or how it should behave differently
instead of the
bind
'saccept-proxy
option, it's possible to configuretcp-request connection expect-proxy layer4 if { src 192.168.1.0/24 }
. see documentation for reference: https://docs.haproxy.org/2.4/configuration.html#4.2-tcp-request%20connectionhaproxytech ingress controller already supports the
expect-proxy
with a list of CIDRs: https://www.haproxy.com/documentation/kubernetes/latest/community/configuration-reference/configmap/#proxy-protocolhaproxytech/kubernetes-ingress@8c898cb
The text was updated successfully, but these errors were encountered: