Bug 1470214 - [DOCS] openshift_master_default_subdomain should not include master hostname
[DOCS] openshift_master_default_subdomain should not include master hostname
Status: NEW
Product: OpenShift Container Platform
Classification: Red Hat
Component: Documentation (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Vikram Goyal
Vikram Goyal
Vikram Goyal
Depends On:
  Show dependency treegraph
Reported: 2017-07-12 10:14 EDT by Steven Walter
Modified: 2017-07-12 10:14 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Steven Walter 2017-07-12 10:14:34 EDT
Document URL: 

Section Number and Name: 
Configuring Cluster Variables

Describe the issue: 
When openshift_master_default_subdomain is set to a wildcard that the master url or master public url falls into, this can cause misrouting of traffic that should go to the masters to instead go to the router. For instance, if my subdomain is:


And my master URL is:


Then OpenShift components/apps might try to route this traffic to the router (since it fits the wildcard subdomain) instead of the master itself.

Suggestions for improvement: 
Include a statement: "This should not be a pattern that the openshift_master_cluster_hostname or openshift_master_cluster_public_hostname applies to. For instance, with a openshift_master_cluster_hostname of 'master.ocp.example.com', a subdomain '*.ocp.example.com' should not be used as this can cause routing conflicts. Instead use a more specific subdomain, such as '*.apps.ocp.example.com'."

Additional information: 
Fixing this docs bug would prevent potential configuration issues, such as with metrics and logging as described in these trackers.

Note You need to log in before you can comment on or make changes to this bug.