-
Epic
-
Resolution: Done
-
Major
-
None
-
None
-
OCM UI - ROSA support preexisting Route53 for BYO VPC clusters
-
3
-
False
-
False
-
None
-
0% To Do, 0% In Progress, 100% Done
We will need to provide the customer with a flag to let them indicate they will need to use a preexisting Route53 hosted zone. This only applies to BYO-VPC clusters in both OSD and ROSA. The requirement for needing to use a preexisiting Route53 hosted zone is limited to only Shared VPCs (https://docs.aws.amazon.com/whitepapers/latest/building-scalable-secure-multi-vpc-network-infrastructure/amazon-vpc-sharing.html). This is not the same thing as having multiple clusters shared in the same VPC, it's a separate type of architecture where AWS Account A creates the VPC and shares it with AWS Account B. AWS Account B is the customer installing the cluster, and the Route53 hosted zone needs to be created by AWS Account A.
With this flag enabled (checkbox I'm guessing), we will provide the customer with a base domain that we require the customer to configure, along with a link to documentation that explains how to use it.
Once installation is initiated, we need to show the cluster installation as PENDING waiting on the creation of the Route53 hosted zone.
Updated mockups: https://marvelapp.com/prototype/iec55f7/screen/88394549
- is blocked by
-
PD-987 Support preexisting Route53 for BYO VPC in AWS CCS clusters UX
-
- Closed
-
- relates to
-
HAC-4923 [ROSA Wizard] The help link related to shared VPC broken from OCM UI
-
- Closed
-
-
HAC-4925 [ROSA Wizard] Cluster roles and policies step definition didn't respect the change VPC definition from networking step
-
- Closed
-
-
HAC-4926 [ROSA Wizard]Hide Shared VPC options for unsupported OCP version from wizard
-
- Closed
-
- mentioned on