-
Story
-
Resolution: Unresolved
-
Major
-
None
-
None
-
None
-
Product / Portfolio Work
-
False
-
-
False
-
8
-
None
-
None
-
CORENET Sprint 269, CORENET Sprint 270, CORENET Sprint 271
- add a label to the namespace, this will be used by Miciah on router side
- then I will add a specific LRP to specifically redirect haproxy traffic to mp0 in default network
- we will also pkt_mark this packet before sending it out out mp0
- a new controller that watches for namespaces that have routes will be added and if a namespace has a route created then we will match on the mark in br-ex and that traffic alone to the specific UDN's clusterIP will be allowed for haproxy -> this will only be in ocp/ovnk btw
Goal here is to ensure ingress pods can talk to services on UDN networks for routes to work.
Implementation of a solution for host-networked router pods is handled separately as a next step in https://issues.redhat.com/browse/SDN-5665
There is a dependency on net-edge work [Jira LINK TO BE ADDED]
- blocks
-
MTV-3262 [OCP] Support mapping to primary user-defined networks
-
- New
-
- depends on
-
CORENET-4992 [ocp/routes] [Routes] Add support for forwarding HAProxy traffic via service CIDR
-
- To Do
-
- is cloned by
-
CORENET-5662 [ocp/ovn-kubernetes] [Routes] Add special support for ocp-ingress namespace to access any service via mp0: host-networked router pods
-
- To Do
-
- is depended on by
-
CORENET-5662 [ocp/ovn-kubernetes] [Routes] Add special support for ocp-ingress namespace to access any service via mp0: host-networked router pods
-
- To Do
-
-
CORENET-5669 [ocp/ovn-kubernetes] [Routes] Add special support for ocp-ingress namespace to access any service via mp0: upstream E2E tests
-
- To Do
-
-
CORENET-5789 [ocp/ovn-kubernetes] [Routes] Add special support for ocp-ingress namespace to access any service via mp0: openshift E2E tests
-
- To Do
-
- links to