Skip to content

pkg/asset/installconfig/basedomain: Document cluster-name subdomains#630

Merged
openshift-merge-robot merged 1 commit intoopenshift:masterfrom
wking:improve-docs-for-cluster-name-base-domain-interaction
Nov 8, 2018
Merged

pkg/asset/installconfig/basedomain: Document cluster-name subdomains#630
openshift-merge-robot merged 1 commit intoopenshift:masterfrom
wking:improve-docs-for-cluster-name-base-domain-interaction

Conversation

@wking
Copy link
Member

@wking wking commented Nov 7, 2018

@brianredbeard says:

The third time I had to abort was when prompted for base domain followed by cluster name (I included my cluster name in my base domain because I'm using a well structure name server delegation structure).

And I've seen a number of other cases where folks suggest including the cluster name again in the base domain. Sometimes you might need to do that (e.g. if you cannot create subdomains without the additional namespacing). But in most cases, including the cluster name in the base domain is redundant.

Brian says [1]:

  The third time I had to abort was when prompted for base domain
  followed by cluster name (I included my cluster name in my base
  domain because I'm using a well structure name server delegation
  structure).

And I've seen a number of other cases where folks suggest including
the cluster name again in the base domain.  Sometimes you might need
to do that (e.g. if you cannot create subdomains without the
additional namespacing).  But in most cases, including the cluster
name in the base domain is redundant.

[1]: openshift#627 (comment)
@openshift-ci-robot openshift-ci-robot added size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Nov 7, 2018
@abhinavdahiya
Copy link
Contributor

Not sure what's happening here, why do people assume cluster name to be part of the base domain? Even if they do we need the cluster name to create other dns entries...

@wking
Copy link
Member Author

wking commented Nov 7, 2018

At least @vrutkovs has done the same thing. I think a bit of extra docs around this would help. Maybe @brianredbeard or @vrutkovs can speak to whether this change would have helped them?

@vrutkovs
Copy link
Contributor

vrutkovs commented Nov 7, 2018

I remember doing exactly that before etcd discovery landed, so some clarification won't hurt

@abhinavdahiya
Copy link
Contributor

I think we should improve the info, but just curious as to why basedomain implies dns domain with clustername ?

@wking
Copy link
Member Author

wking commented Nov 7, 2018

I think we should improve the info, but just curious as to why basedomain implies dns domain with clustername ?

Domains used by the installed cluster will all be subdomains of the base domain. Those subdomains will all include the cluster name. ${something_with_the_cluster_name}.${base_domain}. That's what I'm trying to express with:

All DNS records will be sub-domains of this base and will also include the cluster name.

but maybe the wording could be improved? Suggestions?

@abhinavdahiya
Copy link
Contributor

fine for now.

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Nov 8, 2018
@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: abhinavdahiya, wking

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:
  • OWNERS [abhinavdahiya,wking]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-merge-robot openshift-merge-robot merged commit e64a43d into openshift:master Nov 8, 2018
@wking wking deleted the improve-docs-for-cluster-name-base-domain-interaction branch November 8, 2018 04:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants