[RHOCP 4] The PodNetworkConnectivityCheck is reporting "no route to host" errors for endpoints that are not available in the cluster.
Issue
-
PodNetworkConnectivityCheck
reports "no route to host" errors for unavailable cluster endpoints.lastTransitionTime: "2023-03-xxT04:xx:xxZ" message: 'network-check-target-xxxxxxxx-xxxxx-monitoring-xxxxx: failed to establish a TCP connection to 10.xxx.2.xx:8080: dial tcp 10.xxx.2.xx:8080: connect: no route to host' reason: TCPConnectError status: "False" type: Reachable failures:
- When using the
-o yaml
option, some of thePodNetworkConnectivityCheck
instances do not display the status section.
Environment
- Red Hat OpenShift Container Platform
- 4
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.