We have an escalation for a customer case where after upgrading to OCP 4.14 they started to see application traffic degradation that seems to be related to the new version of the HAProxy that changed from 2.2.24 to 2.6.13. 

Was already tested by the customer that if the router pods use the old haproxy-router image from OCP 4.12 the issue disappears.

What was observed is that router pods unexpectedly close HTTP keep-alive connection sending a FIN packet while the client is still sending HTTP requests.

4.14.16 (HAProxy 2.6)

Only on customer clusters.

    1.
    2.
    3.
    

Router pods are unexpectedly terminating Keep-alive connections.

Router pods should not terminate a keep-live connection when requests are still coming.

- Was already tried to change the hard-stop to 20m
- Was already tried to change the reload interval to the maximum (2m)
- Was already tried to set `no option idle-close-on-response` in the defualt section of the HAProxy configuration
- Was already verified that content-length headers have a value grater than 0 in the HTTP requests.