Uploaded image for project: 'OpenShift Hosted Control Plane'
  1. OpenShift Hosted Control Plane
  2. HOSTEDCP-100

Allow direct ingress on guest clusters on AWS

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • None
    • None
    • None
    • BU Product Work
    • False
    • False
    • OCPSTRAT-81 - Define and Consolidate HyperShift API Definitions
    • Undefined
    • 0
    • 0
    • 0

      Currently we proxy guest cluster ingress through the management cluster. This assumes the management cluster and guest cluster share a base domain.

      We should allow direct ingress on the guest cluster and have no assumptions about the ingress base domain of the guest cluster.

       

      Required tasks: 

      •  AWS Instances for the guest cluster are not being added to the ELB created as a result of the router-default Service. I think this is a "Cluster Name" vs "Infra ID" cluster ownership tagging issue. Fixed in #95
      •  We don't deploy the CCO so dns_controller in the ingress operator isn't able to make calls against Route53 Fixed in #111 #117 #120
      •  Determine how to make e2e pass with this. Not sure how to discover the base-domain in the CI environment.
      •  Implement destroy for private zone

      References

      https://github.com/openshift/hypershift/pull/94 

            sjenning Seth Jennings
            sjenning Seth Jennings
            He Liu He Liu
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: