Description of problem: Due to the need to map hostnames received from DHCP with the etcd-[0,1,2] DNS records, we have imposed restrictive requirements on the format of the hostnames for the master nodes. Many deployers will want to name their servers based on an internal scheme, so we need to eliminate these restrictions.
In 4.4 the cluster-etcd-operator was added, which should allow us to bootstrap the etcd cluster using the master hostnames directly and drop the etcd-specific records. However, some changes to the baremetal pod configurations are needed for that to work and we need to drop some hard-coded overrides in the coredns-mdns plugin.
Verified on 4.5.0-0.nightly-2020-04-14-031010
[core@master-0-0 ~]$ host -t SRV _etcd-server-ssl._tcp.ocp-edge-cluster.qe.lab.redhat.com
Host _etcd-server-ssl._tcp.ocp-edge-cluster.qe.lab.redhat.com not found: 3(NXDOMAIN)
[core@master-0-0 ~]$ host -t SRV _etcd-server-ssl._tcp.ocp-edge-cluster-0.qe.lab.redhat.com
_etcd-server-ssl._tcp.ocp-edge-cluster-0.qe.lab.redhat.com has SRV record 0 10 2380 master-0-2.ocp-edge-cluster-0.qe.lab.redhat.com.
_etcd-server-ssl._tcp.ocp-edge-cluster-0.qe.lab.redhat.com has SRV record 0 10 2380 master-0-1.ocp-edge-cluster-0.qe.lab.redhat.com.
_etcd-server-ssl._tcp.ocp-edge-cluster-0.qe.lab.redhat.com has SRV record 0 10 2380 master-0-0.ocp-edge-cluster-0.qe.lab.redhat.com.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.