Uploaded image for project: 'OpenShift UX Product Design'
  1. OpenShift UX Product Design
  2. PD-1515

UX work for Support preexisting Route53 for BYO VPC clusters

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • UX work for Support preexisting Route53 for BYO VPC clusters
    • False
    • None
    • False
    • To Do
    • XCMSTRAT-102 - Support preexisting Route53 for Shared VPC clusters
    • 0% To Do, 0% In Progress, 100% Done

      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."

       

      • 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

      Design doc: https://docs.google.com/document/d/1vYgdxLq0mXBRpZZGNTAaqSHCx2_ckJnkdpI-iltt0xg/edit?usp=sharing

              llyman@redhat.com Lisa Lyman
              pkreuser Peter Kreuser
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: