How could we handle maintain long connection does not cut down between external application and ingress when service endpoints changed

[flyfax]

We have an external application, it will create and keep a long connection to a service running in Kubernetes cluster.
The problem we saw is when the service running in Kubernetes auto scaling up, the endpoints updated. It looks HAProxy did the soft-drop first to reload the endpoints change first, then did hard-drop after soft-drop timeout. On our external application side, we saw connection pipeline broken in the log ( Even we have a re-connection mechanism in the application which will reconnect to the service)

We use Haproxy-ingress v3.1.7 with gatewayapi and tcproute configured in Kubernetes cluster

The question would be, is there a way that Haproxy ingress could keep that long connection when HAProxy reload the configuration changes? Thanks.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.