User Story

As a user, I want to use my preexisting Route53 when installing AWS CCS clusters in existing VPC so that I can install into "Shared VPCs" [1] which do not allow the user ("participant") of the shared VPC to automatically (using OpenShift IPI, for example) create Route53 private zones.

[1] https://docs.aws.amazon.com/vpc/latest/userguide/vpc-sharing.html

"Participants cannot directly associate one of their private hosted zones with the shared VPC."

Acceptance Criteria

• api.openshift.com supports hostedZone as an available attribute for BYO VPC clusters
• OCM UI can prompt for a hostedZone field for BYO VPC clusters
• ROSA CLI supports hostedZone as an available attribute for BYO VPC clusters
• OCM CLI supports hostedZone as an available attribute for BYO VPC clusters

Default Done Criteria

• All existing/affected SOPs have been updated.
• New SOPs have been written.
• Internal training has been developed and delivered.
• The feature has both unit and end to end tests passing in all test
  pipelines and through upgrades.
• If the feature requires QE involvement, QE has signed off.
• The feature exposes metrics necessary to manage it (VALET/RED).
• The feature has had a security review.* Contract impact assessment.
• Service Definition is updated if needed.* Documentation is complete.
• Product Manager signed off on staging/beta implementation.

Dates

Integration Testing:
Beta:
GA:

Current Status

GREEN | YELLOW | RED
GREEN = On track, minimal risk to target date.
YELLOW = Moderate risk to target date.
RED = High risk to target date, or blocked and need to highlight potential
risk to stakeholders.

References

Links to Gdocs, github, and any other relevant information about this epic.