Bug 1286861 - Example router and registry is not setup in a specific region or zone
Example router and registry is not setup in a specific region or zone
Status: NEW
Product: OpenShift Container Platform
Classification: Red Hat
Component: Documentation (Show other bugs)
3.1.0
Unspecified Unspecified
medium Severity medium
: ---
: ---
Assigned To: Vikram Goyal
Vikram Goyal
Vikram Goyal
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-11-30 17:40 EST by Eric Jones
Modified: 2017-09-07 16:47 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Eric Jones 2015-11-30 17:40:07 EST
Document URL: 
https://access.redhat.com/documentation/en/openshift-enterprise/version-3.1/installation-and-configuration/#deploying-a-docker-registry

https://access.redhat.com/documentation/en/openshift-enterprise/version-3.1/installation-and-configuration/#haproxy-router

Section Number and Name: 
2.5.2. Deploying the Registry

2.6.3. Deploying the Default HAProxy Router

Describe the issue: 
Documentation examples do not use or show the use of --selector to put these pods on specific node. 

Suggestions for improvement: 
Either, include --selector as its own entry, which I believe is the intent of bug 1281926, or show it with the router and registry as multiple customer have tried to put it on the master but do not know how.

Additional information: 
"Blocked" on bug 1286858 as this wouldn't make sense if we simply remove the putting masters into infra region.

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