-
Epic
-
Resolution: Unresolved
-
Critical
-
None
-
routed-ingress-udn
-
Incidents & Support
-
77
-
- Release note announcing this support
- Downstream test automation verifying that this SDN feature integrates well with VMs (including live migration)
-
Yellow
-
In Progress
-
18% To Do, 9% In Progress, 73% Done
-
Goal
Allow access to primary UDN endpoints through mere routing, with routes advertised using BGP.
This is a CNV tracker for CORENET-4923, implementing RFE-5459. This feature will require re-addressing of VMs on their import to OCP, see OCPSTRAT-1963 if you need to preserve IPs.
Non-Requirements
- <List of things not included in this epic, to alleviate any doubt raised during the grooming process.>
Notes
- <Any additional details or decisions made/needed>
- clones
-
CNV-4600 CNV Epic Template
-
- New
-
- depends on
-
CORENET-5350 [4.20] GA OVN Kubernetes support for BGP as a routing protocol: On-Prem
-
- Closed
-
-
CORENET-4923 Support of routed ingress for L2 UDN: VM Workloads
-
- Closed
-
- is duplicated by
-
CNV-32183 OVN Kubernetes in CNV: Static public IP on Pod network
-
- Closed
-
- relates to
-
OCPSTRAT-1343 Support of routed ingress for L2 UDN: VM Workloads
-
- In Progress
-
- links to
1.
|
automated tests |
|
New | |
Unassigned |
2.
|
downstream documentation merged |
|
New | |
Unassigned |