Uploaded image for project: 'OpenShift Installer'
  1. OpenShift Installer
  2. CORS-2564

Azure NAT Gateway support

    XMLWordPrintable

Details

    • Epic
    • Resolution: Done
    • Major
    • openshift-4.14
    • None
    • None
    • Add Azure NAT Gateway support for Control Plane
    • False
    • None
    • False
    • OCPSTRAT-578Add support to NAT Gateway as outboundType for clusters in Azure (Technology Preview)
    • Yellow
    • To Do
    • OCPSTRAT-578 - Add support to NAT Gateway as outboundType for clusters in Azure (Technology Preview)
    • 100
    • 100% 100%
    • Hide

      15/August/2023

      Color Status: Red

      The CPMS PR merged. The PR for multi zone works well in testing. Target is now 4.15.

       

      8/Auguest/2023

      Color Status: Yellow

      The PR is in good shape, waiting for API PR to merge and for QE to test. Once API PR merges, can do review and change to green.

       

      31/July/2023
      Color Status: Yellow
      Currently looking into how to address issues with private clusters. Right now we can only use a single load balancer due to naming problems.

      28/April/2023
      The work for this and multiple backend pools is mostly complete. I (John) can probably safely remove the spike since the PoC's have already been completed.

      Show
      15/August/2023 Color Status: Red The CPMS PR merged. The PR for multi zone works well in testing. Target is now 4.15.   8/Auguest/2023 Color Status: Yellow The PR is in good shape, waiting for API PR to merge and for QE to test. Once API PR merges, can do review and change to green.   31/July/2023 Color Status: Yellow Currently looking into how to address issues with private clusters. Right now we can only use a single load balancer due to naming problems. 28/April/2023 The work for this and multiple backend pools is mostly complete. I (John) can probably safely remove the spike since the PoC's have already been completed.

    Description

      Epic Goal

      • Control Plane hosts should allow NAT Gateway for Internet egress for purposes of pulling images etc

      Why is this important?

      Scenarios

      1. Install a new cluster, control plane hosts access the Internet via NAT Gateway rather than via the public load balancer
      2. Install a new cluster, with user defined routing, control plane hosts access Internet via previously available UDR
      3. Upgraded clusters maintain their existing architecture

      Acceptance Criteria

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

      Open questions::

      1. Control plane hosts are a must, but likely should just NAT gateway for all, need to understand pros/cons of doing so
      2. It'd be nice to understand what a potential migration for legacy clusters to the new architecture looks like and what options we have to automate that in a non disruptive manner.

      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>

      Attachments

        Activity

          People

            rdossant Rafael Fonseca dos Santos
            rhn-support-sdodson Scott Dodson
            Jinyun Ma Jinyun Ma
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: