Just after installing gloo with the default parameters, the debug log is flooded with messages like:
{"level":"debug","ts":"2022-03-29T10:38:07.976Z","logger":"gateway.v1.event_loop.gateway","caller":"k8sadmission/validating_admission_webhook.go:154","msg":"validation-webhook-server2022/03/29 10:38:07 http: TLS handshake error from 10.36.1.1:51810: EOF\n","version":"1.11.0-rc3"}
It doesn't look like a real issue, maybe a connection closed prematurely. In any case it is polluting the log and it is very difficult to tell for sure the harmful from the harmless entries.
This issue has been marked as stale because of no activity in the last 180 days. It will be closed in the next 180 days unless it is tagged "no stalebot" or other activity occurs.
Gloo Edge Version
1.11.x (beta)
Kubernetes Version
1.21.x
Describe the bug
Just after installing gloo with the default parameters, the debug log is flooded with messages like:
{"level":"debug","ts":"2022-03-29T10:38:07.976Z","logger":"gateway.v1.event_loop.gateway","caller":"k8sadmission/validating_admission_webhook.go:154","msg":"validation-webhook-server2022/03/29 10:38:07 http: TLS handshake error from 10.36.1.1:51810: EOF\n","version":"1.11.0-rc3"}
It doesn't look like a real issue, maybe a connection closed prematurely. In any case it is polluting the log and it is very difficult to tell for sure the harmful from the harmless entries.
Steps to reproduce the bug
Expected Behavior
I expect the debug log to show TLS error only when there is something wrong with certificates.
Additional Context
No response