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

AWS: Cross-Account Shared VPC Installs

XMLWordPrintable

    • AWS Shared VPC
    • BU Product Work
    • False
    • None
    • False
    • Green
    • Done
    • OCPSTRAT-377 - Support preexisting Route53 for Shared VPC clusters
    • OCPSTRAT-377Support preexisting Route53 for Shared VPC clusters
    • 0% To Do, 0% In Progress, 100% Done
    • Hide

      27/July/2023:
      Color status: green
      Done. Working on backporting in: https://issues.redhat.com/browse/OCPSTRAT-659

      6/July/2023
      Color status: green
      Still figuring out CI permissions issue. Will begin backporting soon.

      29/June/2023
      Color Status: Green
      CI is mostly complete, but need DPP to increase permissions for the CI credential. Ticket was opened yesterday. We need CI testing in place to get TRT to remove the techpreview flag. Backporting should begin soon.

      16/June/2023
      Color status: green

      28/April/2023
      Color status: green
      Actively working on spike

      Show
      27/July/2023: Color status: green Done. Working on backporting in: https://issues.redhat.com/browse/OCPSTRAT-659 6/July/2023 Color status: green Still figuring out CI permissions issue. Will begin backporting soon. 29/June/2023 Color Status: Green CI is mostly complete, but need DPP to increase permissions for the CI credential. Ticket was opened yesterday. We need CI testing in place to get TRT to remove the techpreview flag. Backporting should begin soon. 16/June/2023 Color status: green 28/April/2023 Color status: green Actively working on spike

      OCP/Telco Definition of Done
      Epic Template descriptions and documentation.

      <--- Cut-n-Paste the entire contents of this description into your new Epic --->

      Epic Goal

      • Enable/confirm installation in AWS shared VPC scenario where Private Hosted Zone belongs to an account separate from the cluster installation target account

      Why is this important?

      • AWS best practices suggest this setup

      Scenarios

      1. ...

      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>

              padillon Patrick Dillon
              padillon Patrick Dillon
              Yunfei Jiang Yunfei Jiang
              Votes:
              0 Vote for this issue
              Watchers:
              12 Start watching this issue

                Created:
                Updated:
                Resolved: