F5 is upgrading its customer support chat feature on My.F5.com. Chat support will be unavailable from 6am-10am PST on 1/20/26. Refer to K000159584 for details.

Forum Discussion

Genna_Reingold's avatar
Genna_Reingold
Icon for Nimbostratus rankNimbostratus
Mar 12, 2025

Health Monitor unable to connect to OpenShift Router

Hi, We have F5 VS routing traffic to a service behind OpenShift Router ( We are not using F55  CIS ). The OpenShift Route is configured as TLS Passthrough.    I want to re-encrypt TLS at F5. In cas...
openshift
BramsBytes's avatar
BramsBytes
Icon for Cirrus rankCirrus
Mar 16, 2025

In our environment we use custom HTTPS monitors where we specify the Host: header. This allows the OpenShift router to reach the application.

 

GET /favicon.ico HTTP/1.1\r\nHost: my-tls-passtrough-service.com\r\nConnection: Close\r\n\r\n

Genna_Reingold's avatar
Genna_Reingold
Icon for Nimbostratus rankNimbostratus
Mar 16, 2025

Hi BramsBytes 
Thanks. Yes we have done it too, but it doesn't work. Not that I have expected it to work  - when route  in OpenShift is configured as TLS passthrough the routing host information is taken from TLS Client Hello Message not from HTTP Host Header 

  • BramsBytes's avatar
    BramsBytes
    Icon for Cirrus rankCirrus
    Mar 16, 2025

    I see, and in the ServerSSL profile you did also specify the Server Name to be used for Client Hello?

    • Genna_Reingold's avatar
      Genna_Reingold
      Icon for Nimbostratus rankNimbostratus
      Mar 16, 2025

      Yes. Correct 
      And that what allowed the connection through.
      So the requests are routed correctly through the VS using ServerSSL profile with host name in it.  But Health checks configured with the same ServerSSL profile are failing