Bug 1318078 - [openshift-doc] Documentation should explains about router pod deployment during advanced installation
Summary: [openshift-doc] Documentation should explains about router pod deployment dur...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Documentation
Version: 3.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: ---
Assignee: Vikram Goyal
QA Contact: Vikram Goyal
Vikram Goyal
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-16 01:04 UTC by Kenjiro Nakayama
Modified: 2019-10-10 11:33 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-06 05:19:51 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Kenjiro Nakayama 2016-03-16 01:04:22 UTC
Document URL:

- https://docs.openshift.com/enterprise/3.1/install_config/install/advanced_install.html
- https://docs.openshift.org/latest/install_config/install/advanced_install.html#configuring-ansible

Section Number and Name:

- Needs a new section or a side note.

Describe the issue:

- Current advanced installation deploys router pod by default. It should be documented.

Suggestions for improvement:

- same as above "Describe the issue".

Additional information:

- It also should say the condition of the router. e.g) it will be deployed on the node which has 'region=infra'.

Comment 2 brice 2017-12-06 05:19:51 UTC
This looks like it has been added to the 3.1 docs since:

https://docs.openshift.com/enterprise/3.1/install_config/install/advanced_install.html#configuring-node-host-labels

This is maintained through to the 3.7 docs (though under a newer "Deploying the Router to a Labeled Node" section):

https://docs.openshift.com/container-platform/3.7/install_config/router/default_haproxy_router.html#basic-router-commands

I don't think anymore information needs to be added. I'll close this BZ.

Kenjiro, if you disagree, please let me know.


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