Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-62299

The "kube-rbac-proxy-web" container reporting TLS handshake error

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • 4.18.z, 4.19, 4.20
    • apiserver-auth
    • None
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • Moderate
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Description of problem:

      The kube-rbac-proxy-web running in the "alert-manager" pod is showing errors:

      $ oc logs alertmanager-main-0 -c kube-rbac-proxy-web |tail -n2

2025-09-25T19:48:18.538959699Z I0925 19:48:18.538885       1 log.go:245] http: TLS handshake error from <IP>:42930: write tcp <IP>:9095-><IP>:42930: write: connection reset by peer
2025-09-25T19:48:19.255619320Z I0925 19:48:19.255539       1 log.go:245] http: TLS handshake error from <IP>:49036: write tcp <IP>:9095-><IP>:49036: write: connection reset by peer

      Both alert manager pods are having the same errors. The error is show for 2 ips only, and both are linked to the openshift ingress router pods.

      Same as in the issue: https://issues.redhat.com/browse/OCPBUGS-5916

      There is no other visible issue for this.

      Version-Release number of selected component (if applicable):

      OpenShift 4.18.21

      How reproducible:

      100% of the time

      Steps to Reproduce:

          1. Spin up a 4.18.21 cluster
    2. Check AM's KRP web container.

              Unassigned Unassigned
              rhn-support-vwalek Vladislav Walek
              None
              None
              Junqi Zhao Junqi Zhao
              None
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: