Uploaded image for project: 'OpenShift Request For Enhancement'
  1. OpenShift Request For Enhancement
  2. RFE-5775

Automatic DNS Management for additional IngressControllers.

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • Network Edge
    • None
    • False
    • None
    • False
    • Not Selected

      1. Proposed title of this feature request

      Automatic DNS Management for additional IngressControllers.
      2. What is the nature and description of the request?

      The customer has additional ingress controllers, which are configured with different domains from the default domain. 
      The customer wants the automatic DNS Management for additional IngressControllers. Our understanding is that automatic DNS Management is possible only for Default Ingress tied to BaseDomain for a cluster deployed on AWS.

       DNS management for Default IngressController with BaseDomain is managed by adding the wildcard entry in route53, mapping it to the load balancer when creating the IngressController.
       
      In a similar way, we want to manage the automatic DNS Management for additional IngressControllers.

      3. Why does the customer need this? (List the business requirements here)

      The customer has multiple ingress controllers, and they are tied to different domains. They want automatic DNS management for it.

      4. List any affected packages or components.

      OpenShift Networking

              mcurry@redhat.com Marc Curry
              njajodia Nirjhar Jajodia (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: