Uploaded image for project: 'OpenShift Container Platform (OCP) Strategy'
  1. OpenShift Container Platform (OCP) Strategy
  2. OCPSTRAT-1745

Support Intracluster UDN Interconnectivity

XMLWordPrintable

    • Strategic Product Work
    • False
    • Hide

      None

      Show
      None
    • False
    • OCPSTRAT-1247OpenShift Networking Universal Connectivity
    • 100% To Do, 0% In Progress, 0% Done
    • 0

      Feature Overview (aka. Goal Summary)  

      Support configurable traffic between 2 or more consensual but otherwise-isolated User Defined Networks (UDNs) on the same OpenShift cluster. 

      Goals (aka. expected user outcomes)

      Configurable traffic interconnect between UDNs that allows specification of consensual UDNs and the specific type and direction(s) of traffic that is allowed. 

      Requirements (aka. Acceptance Criteria):

      Anyone reviewing this Feature needs to know which deployment configurations that the Feature will apply to (or not) once it's been completed.  Describe specific needs (or indicate N/A) for each of the following deployment scenarios. For specific configurations that are out-of-scope for a given release, ensure you provide the OCPSTRAT (for the future to be supported configuration) as well.

      Deployment considerations List applicable specific needs (N/A = not applicable)
      Self-managed, managed, or both  
      Classic (standalone cluster)  
      Hosted control planes  
      Multi node, Compact (three node), or Single node (SNO), or all  
      Connected / Restricted Network  
      Architectures, e.g. x86_x64, ARM (aarch64), IBM Power (ppc64le), and IBM Z (s390x)  
      Operator compatibility  
      Backport needed (list applicable versions)  
      UI need (e.g. OpenShift Console, dynamic plugin, OCM)  
      Other (please specify)  

      Use Cases (Optional):

      Questions to Answer (Optional):

       

      Out of Scope

      • Providing cross-cluster interconnect between UDNs.

        Background

      Customers want isolated-by-default UDNs for segmentation/microsegmentation, but would also like the ability to override that isolation and allow specific types of traffic to be permitted between two or more consensual UDNs for a purpose of their own designation.

      Customer Considerations

      Documentation Considerations

      Interoperability Considerations

      • The implementation should continue to honor (Admin) Network Policy configuration.

              mcurry@redhat.com Marc Curry
              mcurry@redhat.com Marc Curry
              Surya Seetharaman, Tim Rozet
              Surya Seetharaman Surya Seetharaman
              Anurag Saxena Anurag Saxena
              Ashley Hardin Ashley Hardin
              Tim Rozet Tim Rozet
              Surya Seetharaman Surya Seetharaman
              Marc Curry Marc Curry
              Chris Fields Chris Fields
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: