-
Feature Request
-
Resolution: Unresolved
-
Undefined
-
None
-
openshift-4.19
-
None
-
None
-
Product / Portfolio Work
-
None
-
False
-
-
None
-
None
-
None
-
-
None
-
None
-
None
-
None
-
None
1. Proposed title of this feature request
Interconnected Intracluster Primary UDNs
2. What is the nature and description of the request?
Ability to connect 2 UDNs between namespaces or within the same namespace
3. Why does the customer need this? (List the business requirements here)
While UDNs provide a default level of isolation and segmentation, customers want the ability to override this behaviour and connect UDNs, as necessary, to allow for specific types of traffic or services to communicate.
Additionally, tied to having multiple primary UDNs in a single namespace, intraconnected UDNs allow for the expansion of an existing address space without having to create and migrate an existing UDN.
This allows an administration to create a primary UDN with an address space that is as small as necessary, without sacrificing future scalability for the workload, tenant or service.
This also gives customers the ability to control the address space advertised into the provider network through BGP by only advertising the required UDNs.
4. List any affected packages or components.
- is incorporated by
-
OCPSTRAT-1745 Support Intracluster UDN Interconnectivity
-
- In Progress
-