OKD 4.9 - Connectivity issues between existing worker node and a remote worker node via service (inside the cluster)

6 views
Skip to first unread message

Kanika Mahajan

unread,
Feb 23, 2023, 4:48:46 AM2/23/23
to okd-wg

Hello,

We have recently installed OKD 4.9 version with 3 master nodes, 1 worker node and 3 storage nodes. In addition to that, we have added 1 remote worker node to our cluster.
But, we are experiencing a connectivity issue between the existing worker nodes and the remote ones.

For example, we deployed an application containing a php and a mysql component in our OKD cluster. But, if these two components (php and mysql) are deployed on pods attached to different nodes, that is, if php pod is on existing worker node and mysql pod is on remote worker, they are unable to communicate using internal service attached to the pod (inside the cluster).

Moreover, on the remote worker node, the internal image registry (image-registry.openshift-image-registry.svc:5000) is inaccessible as it gives the below error when we try to test the connectivity via curl from this remote worker

* Trying 172.30.84.37:5000... * connect to 172.30.84.37 port 5000 failed: No route to host * Failed to connect to image-registry.openshift-image-registry.svc port 5000: No route to host * Closing connection 0 curl: (7) Failed to connect to image-registry.openshift-image-registry.svc port 5000: No route to host

Does anyone has any idea about the issue, we are experiencing?

Thanks in advance!

Reply all
Reply to author
Forward
0 new messages