Goal: 

To allow the designate-operator to add additional targets along with specific mDNS master IPs to the pool update job through a configmap. This is currently specific to the default pool and in support of data plane adoption but should be designed in consideration of future multi-pool and distributed deployments. 

The initial format of the config map will be:

poolname:
 - masters: [list of mDNS ips]
targets:
 - server: ipaddress
rndc: rndc secret name
dnsport: 53 // optional
rndcport: 953 //optional
 - server: ipaddress
....
 - masters: [list of different mDNS]
targets:
-

By allowing multiple lists of masters and targets we can allow for distinct mDNS endpoints to be used with different target BIND9 servers. Initially we only need the one but we may need more in the future for AZ support and making it a list now avoids potential update/upgrade issues. By specifying the pool name, this can be expanded to support multi-pool as well.

If the RHOSO BIND9 count is non-zero, a section of targets will be automatically be created that uses the IP information managed behind the scenes by the operator in addition to those supplied by this config map.

The name of the configmap should be configurable but have a sensible default.

Acceptance Criteria:

bind pool generation and pool update job succeeds. Ideally the worker, mDNS and BIND9 will all work together if the networking is all configured properly.