search

openshift / openshift-docs

OpenShift 3 and 4 product and community documentation
https://docs.openshift.com
Apache License 2.0
746 stars 1.72k forks source link

[enterprise-4.1] DNS record types should be explicit in installing/installing_vsphere/installing-vsphere.adoc #16502

Closed nccurry closed 3 years ago

nccurry commented 5 years ago

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.

nccurry commented 5 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.

nccurry commented 4 years ago

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.

https://docs.openshift.com/container-platform/4.3/installing/installing_bare_metal/installing-bare-metal.html#installation-dns-user-infra_installing-bare-metal

https://docs.openshift.com/container-platform/4.3/installing/installing_vsphere/installing-vsphere.html#installation-dns-user-infra_installing-vsphere

Perhaps a list like organized by record type might be more clear

openshift-bot commented 3 years ago

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

openshift-bot commented 3 years ago

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

openshift-bot commented 3 years ago

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-ci-robot commented 3 years ago

@openshift-bot: Closing this issue.

In response to [this](https://github.com/openshift/openshift-docs/issues/16502#issuecomment-734173312): >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 Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.