Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Use masquerade default gateway when no default gw is found
When no default gateway is found, OVNK will still come up. This behavior was intentional: 3eeb930 The goal was that with design changes, host->service traffic would work without the need for a default gateway to be detected. This works, in most cases, but there is a case we did not consider. If a user has deployed a cluster with local gateway mode, and is using a different interface/network for kapi traffic (not the gateway bridge interface), then endpoints to the kubernetes service will reside on this other network. In this case when a host tries to talk to kube API service, the traffic would go to the GR, it would be DNAT'ed to an IP address not on any known network, and be dropped by OVN routing when there is no default gateway route. When the configuration parameter AllowNoUplink is set, we will set the default route to be the masquerade IP, which solves this problem. This commit changes the behavior to not require AllowNoUplink to be set in order to achieve the same behavior, as services should work in this scenario even without a default gw. Signed-off-by: Tim Rozet <trozet@redhat.com>
- Loading branch information