-
Epic
-
Resolution: Obsolete
-
Major
-
None
-
None
Goal
Provide secondary overlay networks with access to the external network.
User Stories
- As an owner of a VM that is connected only to a secondary overlay network, I want to fetch resources from outside networks (internet).
- I do not want to change my application to support multiple NICs.
Non-Requirements
- Ingress is tracked in
CNV-24258
Notes
- Once we have both ingress and egress, we may be able to obsolete the custom solution on OVN-K introduced for HyperShift.
- depends on
-
SDN-4521 Ingress and egress for OVN Kubernetes secondary networks
- New
-
RFE-4938 Support of egress and Service ingress for secondary OVN Kubernetes networks
- Accepted
- is blocked by
-
CNV-24260 [TP] OVN Kubernetes secondary L2 overlay: IPAM
- Closed
- is cloned by
-
CNV-44224 [GA] OVN Kubernetes: L2 overlay egress
- Closed
- is depended on by
-
CNV-34629 VM-friendly networks on AWS and ROSA (bare metal)
- Backlog
- is documented by
-
CNV-39862 [DP] Document egress attribute
- Closed
- is incorporated by
-
CNV-45524 OVN: Graduating user-defined primary networks in Virtualization
- In Progress
- relates to
-
CNV-24258 OVN Kubernetes: L2 overlay ingress
- Closed
1.
|
upstream roadmap issue | New | Unassigned | ||
2.
|
upstream documentation | New | Unassigned | ||
3.
|
upgrade consideration | New | Unassigned | ||
4.
|
CEE/PX summary presentation | New | Unassigned | ||
5.
|
test plans in polarion | New | Unassigned | ||
6.
|
automated tests | New | Unassigned | ||
7.
|
downstream documentation merged | New | Unassigned |