Uploaded image for project: 'OpenShift Core Networking'
  1. OpenShift Core Networking
  2. CORENET-6086

[TESTING only] Support BGP with OVN-K on AWS (DIY, no integration with native AWS constructs like transit gateway) - Document what breaks

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Done
    • Icon: Critical Critical
    • None
    • None
    • OVN Kubernetes
    • None
    • BGP on AWS
    • Product / Portfolio Work
    • OCPSTRAT-2243R&D Spike: BGP integration on AWS
    • 0% To Do, 0% In Progress, 100% Done
    • False
    • Hide

      None

      Show
      None
    • False
    • Not Selected
    • Hide

      Sep 8, 2025 status:

      Investigating setting up BGP between ocp nodes and AWS transit gateway.

      Sep 1, 2025 status:

      CUDN and egressip testing done. Results can be found in doc. Spikes investigation are in progress.

      Aug 22, 2025 status:

      • Ying: L3 CUDN testing done, testing results is recorded in doc.
      • Jean: egressIP on L3 CUDN is done (egressIP on L2 CUDN is not supported even for BM)
      • Huiran: L2 CUDN testing done.
      • Meina: BGP on node's secondary interface on AWS successfully setup on LGW. I'm testing remaining traffic on LGW and SGW.

      Aug 15, 2025 status:

      • YIng: L3 CUDN testing is in progress and recorded in doc. SGW works as desinged except known issue OCPBUGS-50636. Working on LGW testing.
      • Huiran: L2 CUDN testing is in progress and recorded in doc ;
                     Created a script to configure AWS BGP ENV based on steps in doc ;
                     Spike was created for L2 cudn not able to access external host. ;
                     UDN bug for LGW OCPBUGS-60543;
      • Jean:  all nodes in same zone - tested L3 CUDN egressIP advertisement for SGW and LGW,  with and without nodeSelector, L3 CUDN egressIP advertisement works as designed
      • Meina: with the help of Surya, BGP on node's secondary interface on AWS successfully setup on LGW. And L2 traffic can work well. I will test remaining traffic on LGW and SGW.
      Show
      Sep 8, 2025 status: Investigating setting up BGP between ocp nodes and AWS transit gateway. Sep 1, 2025 status: CUDN and egressip testing done. Results can be found in doc. Spikes investigation are in progress. Aug 22, 2025 status: Ying: L3 CUDN testing done, testing results is recorded in doc. Jean: egressIP on L3 CUDN is done (egressIP on L2 CUDN is not supported even for BM) Huiran: L2 CUDN testing done. Meina: BGP on node's secondary interface on AWS successfully setup on LGW. I'm testing remaining traffic on LGW and SGW. Aug 15, 2025 status: YIng: L3 CUDN testing is in progress and recorded in doc . SGW works as desinged except known issue OCPBUGS-50636 . Working on LGW testing. Huiran: L2 CUDN testing is in progress and recorded in doc ;              Created a script to configure AWS BGP ENV based on steps in doc ;               Spike was created for L2 cudn not able to access external host. ;              UDN bug for LGW OCPBUGS-60543 ; Jean:  all nodes in same zone - tested L3 CUDN egressIP advertisement for SGW and LGW,  with and without nodeSelector, L3 CUDN egressIP advertisement works as designed Meina: with the help of Surya, BGP on node's secondary interface on AWS successfully setup on LGW. And L2 traffic can work well. I will test remaining traffic on LGW and SGW.
    • None
    • None
    • None

      Template:

      Networking Definition of Planned

      Epic Template descriptions and documentation

      Epic Goal

      BGP on AWS on OpenShift

      Whatever was developed and tested in Baremetal during the 4.20/4.19.z release in this epic: https://issues.redhat.com/browse/CORENET-5350 must be supported on AWS. This EPIC is the first step towards that. Test BGP, understand what breaks and document that.

      • default network export/import
      • UDN network export/import
      • VRFLite

      For each of these create SPIKE cards, see what breaks - document it in a TESTING Plan doc with proper diagrams of topology setup.

      OUTCOME: Inform Developers what works and what doesn't. The result of this EPIC will be another EPIC where we can fix the items that don't work

      Why is this important?

      Planning Done Checklist

      The following items must be completed on the Epic prior to moving the Epic from Planning to the ToDo status

      • Priority+ is set by engineering
      • Epic must be Linked to a +Parent Feature
      • Target version+ must be set
      • Assignee+ must be set
      • (Enhancement Proposal is Implementable
      • (No outstanding questions about major work breakdown
      • (Are all Stakeholders known? Have they all been notified about this item?
      • Does this epic affect SD? {}Have they been notified{+}? (View plan definition for current suggested assignee)
        1. Please use the “Discussion Needed: Service Delivery Architecture Overview” checkbox to facilitate the conversation with SD Architects. The SD architecture team monitors this checkbox which should then spur the conversation between SD and epic stakeholders. Once the conversation has occurred, uncheck the “Discussion Needed: Service Delivery Architecture Overview” checkbox and record the outcome of the discussion in the epic description here.
        2. The guidance here is that unless it is very clear that your epic doesn’t have any managed services impact, default to use the Discussion Needed checkbox to facilitate that conversation.

      Additional information on each of the above items can be found here: Networking Definition of Planned

      Acceptance Criteria

      • CI - MUST be running successfully with tests automated
      • Release Technical Enablement - Provide necessary release enablement
        details and documents.

      ...

      Dependencies (internal and external)

      1.

      ...

      Previous Work (Optional):

      1. …

      Open questions::

      1. …

      Done Checklist

      • CI - CI is running, tests are automated and merged.
      • Release Enablement <link to Feature Enablement Presentation>
      • DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
      • DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
      • DEV - Downstream build attached to advisory: <link to errata>
      • QE - Test plans in Polarion: <link or reference to Polarion>
      • QE - Automated tests merged: <link or reference to automated tests>
      • DOC - Downstream documentation merged: <link to meaningful PR>

              rhn-support-yingwang Ying Wang
              ddharwar@redhat.com Deepthi Dharwar (Inactive)
              None
              Huiran Wang, Jaime Caamaño Ruiz, Jean Chen, Zhanqi Zhao
              None
              Steven Smith Steven Smith
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

                Created:
                Updated:
                Resolved: