Vault on OpenShift with haproxy constant [INFO] http: TLS handshake error from xxxx write tcp4 xxxx:8200

I am experiencing an issue with Vault Community Edition running on OpenShift, which is fronted by HAProxy and configured with re-encrypt routes.

The logs are being filled with INFO messages making them difficult to analyze. I tried to diagnose this looking at the configuration.

2024-04-23T15:52:13.685Z [INFO] http: TLS handshake error from IP_OBFUSCATED:55288: write tcp4 IP_OBFUSCATED:8200->IP_OBFUSCATED:55288: write: connection reset by peer
2024-04-23T15:52:13.692Z [INFO] http: TLS handshake error from IP_OBFUSCATED:47054: write tcp4 IP_OBFUSCATED:8200->IP_OBFUSCATED:47054: write: connection reset by peer
2024-04-23T15:52:13.693Z [INFO] http: TLS handshake error from IP_OBFUSCATED:51420: write tcp4 IP_OBFUSCATED:8200->IP_OBFUSCATED:51420: write: connection reset by peer
2024-04-23T15:52:13.720Z [INFO] http: TLS handshake error from IP_OBFUSCATED:56462: write tcp4 IP_OBFUSCATED:8200->IP_OBFUSCATED:56462: write: connection reset by peer
2024-04-23T15:52:13.998Z [INFO] http: TLS handshake error from IP_OBFUSCATED:57252: write tcp4 IP_OBFUSCATED:8200->IP_OBFUSCATED:57252: write: connection reset by peer
2024-04-23T15:52:14.132Z [INFO] http: TLS handshake error from IP_OBFUSCATED:47228: write tcp4 IP_OBFUSCATED:8200->IP_OBFUSCATED:47228: write: connection reset by peer
2024-04-23T15:52:14.155Z [INFO] http2: server: error reading preface from client IP_OBFUSCATED:48454: read tcp4 IP_OBFUSCATED:8200->IP_OBFUSCATED:48454: read: connection reset by peer

Unlike other reports which often cite EOF or bad certificate errors, my primary issue is with “connection reset by peer” errors. I’ve traced these connections and they appear to originate from other load balancers within the cluster, which might be expected given the HAProxy setup.

Could you help me understand if this behavior is typical, or if there’s a potential misconfiguration I should address? Any guidance or insights would be greatly appreciated.

Vault version: 1.15.6

The configuration is using s3 as the storage backend, and mysql for the ha_storage.