Closed nccurry closed 3 years ago
Actually the issue seems to be that PTR records are not needed both for the master hostnames and for the etcd-x names.
Ideally we would have concise list of exactly what records are needed (A, CNAME, SRV, PTR, etc) and their function.
As it stands the current tables for bare-metal and vsphere are not very clear, leading to customer confusion, especially around PTR records.
Perhaps a list like organized by record type might be more clear
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen
.
If this issue is safe to close now please do so with /close
.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle rotten
.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen
.
If this issue is safe to close now please do so with /close
.
/lifecycle rotten /remove-lifecycle stale
Rotten issues close after 30d of inactivity.
Reopen the issue by commenting /reopen
.
Mark the issue as fresh by commenting /remove-lifecycle rotten
.
Exclude this issue from closing again by commenting /lifecycle frozen
.
/close
@openshift-bot: Closing this issue.
Which section(s) is the issue in?
User-provisioned DNS requirements
What needs fixing?
A note needs to be made for each DNS record about which kind of record needs to be created (i.e. A, CNAME, SRV, etc).
The etcd DNS records
etcd-<index>.<cluster_name>.<base_domain>
are supposed to be CNAMES not A records, but this is not spelled out.