Loading...

XML

Word

Printable

Type: Epic
Resolution: Unresolved
Priority: Major
Fix Version/s: None
Affects Version/s: None
Component/s: None
Labels:

Epic Name:
Support Shared VPC AWS infrastructure
Work Type:
BU Product Work
Blocked:
False
Blocked Reason:
None
Ready:
False
Color Status:
Not Selected
Epic Status:
To Do
Feature Link:
OCPSTRAT-1588 - Shared-VPC for Hypershift
Flagged:

Impediment
Parent Link:
OCPSTRAT-1588Shared-VPC for Hypershift
Hierarchy Progress Bar:

11% To Do, 0% In Progress, 89% Done
Release Note Text:

Hide
Per Will G - urgent M7 priority
https://redhat-internal.slack.com/archives/C02LM9FABFW/p1678197351115019

Show
Per Will G - urgent M7 priority https://redhat-internal.slack.com/archives/C02LM9FABFW/p1678197351115019
Target Version:

openshift-4.18

Cost of Delay:
0
WSJF:
0
Risk Score:
0

SFDC Cases Links:
SFDC Cases Counter:
SFDC Cases Open:

Intelligence Requested:
Market:

"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