Uploaded image for project: 'OpenShift Container Platform (OCP) Strategy'
  1. OpenShift Container Platform (OCP) Strategy
  2. OCPSTRAT-377

Support preexisting Route53 for Shared VPC clusters


    • False
    • Hide


    • False
    • 0% To Do, 0% In Progress, 100% Done
    • 0
    • Program Call

      Feature Overview (aka. Goal Summary)  

      Support OpenShift installation in AWS Shared VPC [1] scenario where AWS infrastructure resources (at least the Private Hosted Zone) belong to an account separate from the cluster installation target account.

      Goals (aka. expected user outcomes)

      As a user I need to use a Shared VPC [1] when installing OpenShift on AWS into an existing VPC. Which will at least require the use of a preexisting Route53 hosted zone where I am not allowed the user "participant" of the shared VPC to automatically create Route53 private zones.

      Requirements (aka. Acceptance Criteria):

      The Installer is able to successfully deploy OpenShift on AWS with a Shared VPC [1], and the cluster is able to successfully pass osde2e testing. This will include at least the scenario when private hostedZone belongs to different account (Account A) than cluster resources (Account B)

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

            mak.redhat.com Marcos Entenza Garcia
            mak.redhat.com Marcos Entenza Garcia
            Beth White, James Harrington, Ju Lim, Marc Curry, Marco Braga, Miciah Masters, Patrick Dillon, Will Gordon
            Patrick Dillon Patrick Dillon
            Mike Fiedler Mike Fiedler
            Stephanie Stout Stephanie Stout
            Patrick Dillon Patrick Dillon
            Marcos Entenza Garcia Marcos Entenza Garcia
            Eric Rich Eric Rich
            0 Vote for this issue
            21 Start watching this issue