-
Notifications
You must be signed in to change notification settings - Fork 335
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to debug ovn load balancer? #189
Comments
Unrelated based on the fact that you are running curl from the node, but just in case.
|
It can only be reached from the master where 10.254.72.1 is one of the interfaces. The cluster does not have a gateway configured yet. NAT module seems to be loaded
dump-flows does not give much clue to me apart from saying that the address needs to be NAT'ed.
Another data point. There is another service which points to a pod. That service works from within other pods, but does not work from a host node. |
So, without a gateway configured in a minion, this will not work. The node IP is not in the same virtual address space as the logical switch IPs. They need to exit the virtual space. Or you need to set the --advertise-ip of k8s-api-server as the local mgmt IP of OVN.
The host likely does not have a route to the service IP. If your pod ips are in 192.168.0.0/16 and service IP range is 192.168.200.0/24, it will work because we add a route in the host saying that 192.168.0.0/16 is reachable from local mgmt port. In your case, that is likely not the case. So a route will have to be added. |
Thanks @shettyg, this should have been obvious. Don't know what I was thinking. Closing the issue.
|
OWNERS: sync to CNO
On a cluster with 40 nodes, the service is stored in the ovn load balancer table. But it does not work on some of the nodes. How to debug what is wrong?
The text was updated successfully, but these errors were encountered: