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

embed dns service into cluster

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Done
    • Icon: Blocker Blocker
    • None
    • openshift-4.9, openshift-4.10, openshift-4.11
    • Network Edge

      1. Proposed title of this feature request
      embed dns service into cluster
      2. What is the nature and description of the request?
      To deploy and run a openshift4 cluster, a external dns service is needed, usually it is standalone dns server. The most important part is to resolve api., and api-int.. For baremetal deployment, especially disconnected senario, the HA should be considered for this external dns server, so there should be 2 server to host the dns with VIP. But this solution is complex and hard to maintain.

      Based on a SE ( https://issues.redhat.com/browse/SUPPORTEX-11008 ), we find that we can use power dns, to replace the external dns service with cluster internal compoments. The SE includes an prototype customer solution and QE has tested it and pass the test.

      3. Why does the customer need this? (List the business requirements here)
      This RFE can benifies every openshift4 cluster, to reduce external components dependency, expecially the disconnected senario. But the Edge use case, with UPI installation mode, especially disconnected compact cluster, the number of server is limited under such business senario, reduce the server requirement of the external load balancer is critical for business success.

      4. List any affected packages or components.
      external DNS should set NS record and point to the cluster.

              racedoro@redhat.com Ramon Acedo
              zhengwan1@redhat.com Zheng Wang
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: