Don't log TLS handshake error on health-probe-connections

[ibihim]

What

Add flag that silences logs for shallow tcp connections that are opened and closed.

Why

haproxy makes health probes by opening tcp connections and closing them. kube-rbac-proxy reports a TLS handshake error, when this happens.

Ref

https://bugzilla.redhat.com/show_bug.cgi?id=2111670

[ibihim]

I've looked into the topic, and there aren't any clear solutions available.

While there's a filter for logging, it only applies to the message content. It doesn't seem possible to entirely drop the message.

Given that this is a deep-seated networking error within the Go programming language, adjusting the log verbosity doesn't seem to have any effect.

It's worth noting that the actor initiating the TCP RST is the root of the issue, not the receiver that logs this behavior.