-
Bug
-
Resolution: Obsolete
-
Normal
-
None
-
4.10, 4.14, 4.16
-
None
-
None
-
Rejected
-
False
-
Migrated https://bugzilla.redhat.com/show_bug.cgi?id=2111670
https://bugzilla.redhat.com/show_bug.cgi?id=2111670# PrivateDescription[samy |
mailto:szemmour@redhat.com] 2022-07-27 19:14:29 UTC Description of problem: The kube-rbac-proxy-federate container inside the prometheus-user-workload-0 pod deployed part of the openshift-user-workload-monitoring namespace throw TLS handshake error. |
Version-Release number of selected component (if applicable):
openshift 4.10.22
How reproducible:
Steps to Reproduce:
1. Deploy openshift 4.10.22 cluster
2. Enable monitoring for user-defined projects
3. check logs in the kube-rbac-proxy-federate container:
oc logs prometheus-user-workload-0 -n openshift-user-workload-monitoring -c kube-rbac-proxy-federate
Actual results:
022/07/27 17:06:53 http: TLS handshake error from 10.131.0.3:58912: write tcp 10.129.2.15:9092->10.131.0.3:58912: write: connection reset by peer
2022/07/27 17:06:53 http: TLS handshake error from 10.128.2.10:33522: write tcp 10.129.2.15:9092->10.128.2.10:33522: write: connection reset by peer
2022/07/27 17:06:58 http: TLS handshake error from 10.131.0.3:59010: write tcp 10.129.2.15:9092->10.131.0.3:59010: write: connection reset by peer
2022/07/27 17:06:58 http: TLS handshake error from 10.128.2.10:33596: write tcp 10.129.2.15:9092->10.128.2.10:33596: write: connection reset by peer
2022/07/27 17:07:03 http: TLS handshake error from 10.131.0.3:59084: write tcp 10.129.2.15:9092->10.131.0.3:59084: write: connection reset by peer
Expected results:
No TLS handshake error
Additional info:
This issue happen even if no application is configured to expose metrics|
- causes
-
OCPBUGS-32021 too many "write: connection reset by peer" logs in kube-rbac-proxy-web container logs
- Closed