Uploaded image for project: 'OpenShift Hosted Control Plane'
  1. OpenShift Hosted Control Plane
  2. HOSTEDCP-677

[SPIKE] Support Shared VPC AWS infrastructure

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • None
    • None
    • [SPIKE] Support Shared VPC AWS infrastructure
    • False
    • None
    • False
    • Not Selected
    • To Do
    • XCMSTRAT-338 - Parent feature for all ROSA Parity Epics
    • Impediment
    • XCMSTRAT-338Parent feature for all ROSA Parity Epics
    • 0
    • 0% 0%
    • Show
      Per Will G - urgent M7 priority https://redhat-internal.slack.com/archives/C02LM9FABFW/p1678197351115019
    • 0
    • 0
    • 0

      "Shared VPCs" are a unique AWS infrastructure design: https://docs.aws.amazon.com/vpc/latest/userguide/vpc-sharing.html

      See prior work/explanations/etc here: https://issues.redhat.com/browse/SDE-1239

       

      Summary is that in a Shared VPC environment, a VPC is created in Account A and shared to Account B. The owner of Account B wants to create a ROSA cluster, however Account B does not have permissions to create a private hosted zone in the Shared VPC. So they have to ask Account A to create the private hosted zone and link it to the Shared VPC. OpenShift then needs to be able to accept the ID of that private hosted zone for usage instead of creating the private hosted zone itself.

      QE should have some environments or testing scripts available to test the Shared VPC scenario

       

            rhn-support-jiezhao Jie Zhao
            wgordon.openshift Will Gordon
            Jie Zhao Jie Zhao
            Votes:
            0 Vote for this issue
            Watchers:
            15 Start watching this issue

              Created:
              Updated: