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

Support for Non-Wildcard DNS Entries for Custom Ingress Controllers

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • Network - IngressDNS
    • None
    • None
    • Product / Portfolio Work
    • None
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Currently, OpenShift automatically creates wildcard DNS entries for the default ingress controller. However, for additional custom ingress controllers, one of my customers would prefer not to use wildcard DNS records. Instead, they would like the cluster to handle DNS creation based on the router’s canonical hostname.

      Current Behavior:
      When the cluster provisions DNS records, it automatically creates entries such as:

      *.apps.pd1630.<domain> A 30 api-int.pd1630.<domain> A 60 api.pd1630.<domain> A 60

      This behavior results in the use of wildcard DNS for the applications domain.

      For additional custom ingress controllers, they currently disable automatic DNS management (set to unmanaged) and create the required DNS records manually, since they do not want customers to rely on wildcard entries.


      Expected Behavior / Enhancement Request:
      They would like OpenShift to support the creation of non-wildcard DNS entries for custom ingress controllers.
      Specifically, the router’s canonical hostname should be used as the DNS name, for example:
       
      ~~~
      router-intranet-<cluster-domain>
      ~~~
      This would allow the cluster to manage DNS entries automatically without requiring wildcard records or manual intervention.

              mcurry@redhat.com Marc Curry
              rhn-support-ankhande Anjali Khandelwal
              None
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                None
                None