ivampiresp/longhorn
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Add more descriptions for the default setting doc and the taint tolerations doc

Browse Source 
Some details are not included in the docs and they may confuse users.

Longhorn #805, #806

Signed-off-by: Shuo Wu <shuo@rancher.com>
This commit is contained in:
Shuo Wu 2019-10-09 11:43:06 -07:00 committed by Sheng Yang
parent 768f5138fa
commit 071a465b23
2 changed files with 5 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/customized-default-setting.md
View File

@ -4,6 +4,10 @@
During Longhorn system deployment, users can customize the default settings for Longhorn. e.g. specify `Create Default Disk With Node Labeled` and `Default Data Path` before starting the Longhorn system.
## Usage
### Note:
1. This default setting is only for Longhorn system that hasn't been deployed. And it has no impact on the existing Longhorn system.
2. The users should modify the settings for an existing Longhorn system via UI.
### Via Rancher UI
[Cluster] -> System -> Apps -> Launch -> longhorn -> LONGHORN DEFAULT SETTINGS

3
docs/taint-toleration.md
View File

@ -3,8 +3,7 @@
## Overview
If users want to create nodes with large storage spaces and/or CPU resources for Longhorn only (to store replica data) and reject other general workloads, they can taint those nodes and add tolerations for Longhorn components. Then Longhorn can be deployed on those nodes.
For more Kubernetes taint and toleration info, see:
[Kubernetes Taint & Tolerations](https://kubernetes.io/docs/concepts/configuration/taint-and-toleration/)
Notice that the taint tolerations setting for one workload will not prevent it from being scheduled to the nodes that don't contain the corresponding taints. See [Kubernetes's taint and toleration](https://kubernetes.io/docs/concepts/configuration/taint-and-toleration/) for details.
## Setup
### During installing Longhorn