Uploaded image for project: 'Red Hat OpenStack Services on OpenShift'
  1. Red Hat OpenStack Services on OpenShift
  2. OSPRH-8123

make bind9 and unbound accessible as necessary.

XMLWordPrintable

    • Exposing designate DNS services
    • False
    • Hide

      None

      Show
      None
    • False
    • RHOSSTRAT-441Tech Preview - Designate support for RHOSO Greenfield Deployment
    • Not Selected
    • Proposed
    • Committed
    • In Progress
    • RHOSSTRAT-441 - Tech Preview - Designate support for RHOSO Greenfield Deployment
    • designate-operator-container-1.0.7-6
    • Proposed
    • Proposed
    • 0% To Do, 0% In Progress, 100% Done
    • Important

      For default designate deployments bind9 pods need to be accessible to customer's DNS infrastructure.

      For bind9 external to the podified control plane, the miniDNS services need to be externally accessible for zone transfers.

      The unbound resolver needs to be accessible to OpenStack tenant workloads.

      Some quick notes on acceptance criteria:

      • There are CRD changes involved with most of this so this Epic should not be closed until the functionality is verified with an operator managed by the current main branch of the openstack operator
      • install_yamls related patches are also required to fully test so there is some cross repo work that needs to be completed. These should all be verified as merged.
      • Making the services accessible to clients outside of the cluster will, for customers, involved deployment planning and decisions. The documentation of tasks are essential.
        *

              rhn-engineering-beagles Brent Eagles
              rhn-engineering-beagles Brent Eagles
              rhos-dfg-networking-squad-vans
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: