XML

Word

Printable

Epic Name:
cnv-ovn2k-egress
Activity Type:
Product / Portfolio Work
Acceptance Criteria:
Hide

Everything from ~~CNV-33753~~

(must-have) The whole flow must be based on v1 APIs.
Show
Everything from CNV-33753 (must-have) The whole flow must be based on v1 APIs.
Current Status:
Red
Epic Status:
To Do
Feature Link:
VIRTSTRAT-197 - Networking OVN and UDN Integration
Parent Link:
VIRTSTRAT-197Networking OVN and UDN Integration
Status Summary:

Hide

We won't be delivering this epic with its original acceptance criteria.

Instead of supporting egress on arbitrary secondary network, we will align with the SDN team and focus on "user-defined primary networks". This new network type will...

Show
We won't be delivering this epic with its original acceptance criteria. Instead of supporting egress on arbitrary secondary network, we will align with the SDN team and focus on "user-defined primary networks". This new network type will...

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.

Once we have both ingress and egress, we may be able to obsolete the custom solution on OVN-K introduced for HyperShift.

clones

CNV-33753 [DP] OVN Kubernetes: L2 overlay egress

is depended on by

CNV-34629 VM-friendly networks on AWS and ROSA (bare metal)

is incorporated by

CNV-45524 OVN: Graduating user-defined primary networks in Virtualization

1.	upstream roadmap issue	Closed	Unassigned
2.	upstream documentation	Closed	Unassigned
3.	upgrade consideration	Closed	Unassigned
4.	CEE/PX summary presentation	Closed	Unassigned
5.	test plans in polarion	Closed	Unassigned
6.	automated tests	Closed	Unassigned
7.	downstream documentation merged	Closed	Unassigned