-
Story
-
Resolution: Unresolved
-
Major
-
None
-
None
-
None
-
Product / Portfolio Work
-
False
-
-
False
-
5
-
None
-
None
-
None
This is a continuation of https://issues.redhat.com/browse/SDN-4952 which handled router pods deployed on the CNI network. The focus on this story is for router pods on the host network, which is the case for openshift on Bare Metal.
The design is the same as for SDN-4952 (points 1-4 are reused as is), with the addition of an extra final step:
5. for host-net route pods we will need to add IPT rules for also marking and sending that traffic
Goal here is to ensure host-networked ingress pods can talk to services on UDN networks for routes to work.
- clones
-
CORENET-5202 [ocp/ovn-kubernetes] [Routes] Add special support for ocp-ingress namespace to access any service via mp0: CNI-networked router pods
-
- To Do
-
- depends on
-
CORENET-5202 [ocp/ovn-kubernetes] [Routes] Add special support for ocp-ingress namespace to access any service via mp0: CNI-networked router pods
-
- To Do
-
- is cloned by
-
CORENET-5669 [ocp/ovn-kubernetes] [Routes] Add special support for ocp-ingress namespace to access any service via mp0: upstream E2E tests
-
- To Do
-
- is depended on by
-
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
-