You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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]>
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]>
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]>
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.
The text was updated successfully, but these errors were encountered: