Skip to content
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

OVN+Globalnet: Missing default route in table 150 on all the worker nodes #1982

Closed
Tracked by #97
sridhargaddam opened this issue Aug 25, 2022 · 0 comments · Fixed by #1997
Closed
Tracked by #97

OVN+Globalnet: Missing default route in table 150 on all the worker nodes #1982

sridhargaddam opened this issue Aug 25, 2022 · 0 comments · Fixed by #1997
Assignees
Labels
datapath Datapath related issues or enhancements enhancement New feature or request globalnet OVN

Comments

@sridhargaddam
Copy link
Member

What happened:

In order to support Host networking use-case with Submariner, the OVN route-agent handler programs a default route in table 150 with nexthop that matches with the nexthop on ovn-k8s-mp0 interface. Basically, its to inform that Submariner managed traffic should be forwarded to the ovn_cluster_router and pass through the CNI network and not via the default routes present on the host.

It was seen that when Submariner is deployed with Globalnet enabled on an OVNK cluster this route is missing on all the nodes.

@sridhargaddam sridhargaddam added bug Something isn't working OVN globalnet labels Aug 25, 2022
@sridhargaddam sridhargaddam added enhancement New feature or request datapath Datapath related issues or enhancements and removed bug Something isn't working labels Aug 25, 2022
@sridhargaddam sridhargaddam self-assigned this Sep 1, 2022
sridhargaddam added a commit to sridhargaddam/submariner that referenced this issue Sep 1, 2022
To support hostNetworking use-case the route-agent handler
programs default route in table 150 with nexthop matching
the nexthop on the ovn-k8s-mp0 interface. Basically, we
want the Submariner managed traffic to be forwarded to the
ovn_cluster_router and pass through the CNI network so that
it reaches the active gateway node in the cluster via the
submariner pipeline.

Fixes: submariner-io#1982
Signed-off-by: Sridhar Gaddam <[email protected]>
sridhargaddam added a commit to sridhargaddam/submariner that referenced this issue Sep 1, 2022
To support hostNetworking use-case the route-agent handler
programs default route in table 150 with nexthop matching
the nexthop on the ovn-k8s-mp0 interface. Basically, we
want the Submariner managed traffic to be forwarded to the
ovn_cluster_router and pass through the CNI network so that
it reaches the active gateway node in the cluster via the
submariner pipeline.

Fixes: submariner-io#1982
Signed-off-by: Sridhar Gaddam <[email protected]>
novad03 pushed a commit to novad03/k8s-submariner that referenced this issue Nov 25, 2023
To support hostNetworking use-case the route-agent handler
programs default route in table 150 with nexthop matching
the nexthop on the ovn-k8s-mp0 interface. Basically, we
want the Submariner managed traffic to be forwarded to the
ovn_cluster_router and pass through the CNI network so that
it reaches the active gateway node in the cluster via the
submariner pipeline.

Fixes: submariner-io/submariner#1982
Signed-off-by: Sridhar Gaddam <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
datapath Datapath related issues or enhancements enhancement New feature or request globalnet OVN
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant