chart: Correct the inconsistent for question.yml
Longhorn #2082 Signed-off-by: Shuo Wu <shuo@rancher.com>
This commit is contained in:
parent
d62bcccfc7
commit
2eeb93afb5
@ -58,6 +58,18 @@ questions:
|
|||||||
type: string
|
type: string
|
||||||
label: Longhorn Instance Manager Image Tag
|
label: Longhorn Instance Manager Image Tag
|
||||||
group: "Longhorn Images Settings"
|
group: "Longhorn Images Settings"
|
||||||
|
- variable: image.longhorn.shareManager.repository
|
||||||
|
default: longhornio/longhorn-share-manager
|
||||||
|
description: "Specify Longhorn Share Manager Image Repository"
|
||||||
|
type: string
|
||||||
|
label: Longhorn Share Manager Image Repository
|
||||||
|
group: "Longhorn Images Settings"
|
||||||
|
- variable: image.longhorn.shareManager.tag
|
||||||
|
default: v1_20201204
|
||||||
|
description: "Specify Longhorn Share Manager Image Tag"
|
||||||
|
type: string
|
||||||
|
label: Longhorn Share Manager Image Tag
|
||||||
|
group: "Longhorn Images Settings"
|
||||||
- variable: image.csi.attacher.repository
|
- variable: image.csi.attacher.repository
|
||||||
default: longhornio/csi-attacher
|
default: longhornio/csi-attacher
|
||||||
description: "Specify CSI attacher image repository. Leave blank to autodetect."
|
description: "Specify CSI attacher image repository. Leave blank to autodetect."
|
||||||
@ -158,7 +170,7 @@ questions:
|
|||||||
group: "Longhorn CSI Driver Settings"
|
group: "Longhorn CSI Driver Settings"
|
||||||
- variable: csi.attacherReplicaCount
|
- variable: csi.attacherReplicaCount
|
||||||
type: int
|
type: int
|
||||||
default:
|
default: 3
|
||||||
min: 1
|
min: 1
|
||||||
max: 10
|
max: 10
|
||||||
description: "Specify replica count of CSI Attacher. By default 3."
|
description: "Specify replica count of CSI Attacher. By default 3."
|
||||||
@ -166,7 +178,7 @@ questions:
|
|||||||
group: "Longhorn CSI Driver Settings"
|
group: "Longhorn CSI Driver Settings"
|
||||||
- variable: csi.provisionerReplicaCount
|
- variable: csi.provisionerReplicaCount
|
||||||
type: int
|
type: int
|
||||||
default:
|
default: 3
|
||||||
min: 1
|
min: 1
|
||||||
max: 10
|
max: 10
|
||||||
description: "Specify replica count of CSI Provisioner. By default 3."
|
description: "Specify replica count of CSI Provisioner. By default 3."
|
||||||
@ -174,7 +186,7 @@ questions:
|
|||||||
group: "Longhorn CSI Driver Settings"
|
group: "Longhorn CSI Driver Settings"
|
||||||
- variable: csi.resizerReplicaCount
|
- variable: csi.resizerReplicaCount
|
||||||
type: int
|
type: int
|
||||||
default:
|
default: 3
|
||||||
min: 1
|
min: 1
|
||||||
max: 10
|
max: 10
|
||||||
description: "Specify replica count of CSI Resizer. By default 3."
|
description: "Specify replica count of CSI Resizer. By default 3."
|
||||||
@ -182,7 +194,7 @@ questions:
|
|||||||
group: "Longhorn CSI Driver Settings"
|
group: "Longhorn CSI Driver Settings"
|
||||||
- variable: csi.snapshotterReplicaCount
|
- variable: csi.snapshotterReplicaCount
|
||||||
type: int
|
type: int
|
||||||
default:
|
default: 3
|
||||||
min: 1
|
min: 1
|
||||||
max: 10
|
max: 10
|
||||||
description: "Specify replica count of CSI Snapshotter. By default 3."
|
description: "Specify replica count of CSI Snapshotter. By default 3."
|
||||||
@ -269,10 +281,13 @@ The available modes are:
|
|||||||
default: 3
|
default: 3
|
||||||
- variable: defaultSettings.guaranteedEngineCPU
|
- variable: defaultSettings.guaranteedEngineCPU
|
||||||
label: Guaranteed Engine CPU
|
label: Guaranteed Engine CPU
|
||||||
description: 'Allow Longhorn Instance Managers to have guaranteed CPU allocation. The value is how many CPUs should be reserved for each Engine/Replica Instance Manager Pod created by Longhorn. For example, 0.1 means one-tenth of a CPU. This will help maintain engine stability during high node workload. It only applies to the Engine/Replica Manager Pods created after the setting took effect.
|
description: "Allow Longhorn Instance Managers to have guaranteed CPU allocation. By default 0.25. The value is how many CPUs should be reserved for each Engine/Replica Instance Manager Pod created by Longhorn. For example, 0.1 means one-tenth of a CPU. This will help maintain engine stability during high node workload. It only applies to the Engine/Replica Instance Manager Pods created after the setting took effect.
|
||||||
WARNING: After this setting is changed, all the instance managers on all the nodes will be automatically restarted.
|
In order to prevent unexpected volume crash, you can use the following formula to calculate an appropriate value for this setting:
|
||||||
WARNING: DO NOT CHANGE THIS SETTING WITH ATTACHED VOLUMES.
|
'Guaranteed Engine CPU = The estimated max Longhorn volume/replica count on a node * 0.1'.
|
||||||
By default 0.25.'
|
The result of above calculation doesn't mean that's the maximum CPU resources the Longhorn workloads require. To fully exploit the Longhorn volume I/O performance, you can allocate/guarantee more CPU resources via this setting.
|
||||||
|
If it's hard to estimate the volume/replica count now, you can leave it with the default value, or allocate 1/8 of total CPU of a node. Then you can tune it when there is no running workload using Longhorn volumes.
|
||||||
|
WARNING: After this setting is changed, all the instance managers on all the nodes will be automatically restarted
|
||||||
|
WARNING: DO NOT CHANGE THIS SETTING WITH ATTACHED VOLUMES."
|
||||||
group: "Longhorn Default Settings"
|
group: "Longhorn Default Settings"
|
||||||
type: float
|
type: float
|
||||||
default: 0.25
|
default: 0.25
|
||||||
@ -291,8 +306,15 @@ By default 0.25.'
|
|||||||
default: 300
|
default: 300
|
||||||
- variable: defaultSettings.taintToleration
|
- variable: defaultSettings.taintToleration
|
||||||
label: Kubernetes Taint Toleration
|
label: Kubernetes Taint Toleration
|
||||||
description: 'To dedicate nodes to store Longhorn replicas and reject other general workloads, set tolerations for Longhorn and add taints for the storage nodes. All Longhorn volumes should be detached before modifying toleration settings. We recommend setting tolerations during Longhorn deployment because the Longhorn system cannot be operated during the update. Multiple tolerations can be set here, and these tolerations are separated by semicolon. For example, `key1=value1:NoSchedule; key2:NoExecute`. Because `kubernetes.io` is used as the key of all Kubernetes default tolerations, it should not be used in the toleration settings.
|
description: "To dedicate nodes to store Longhorn replicas and reject other general workloads, set tolerations for Longhorn and add taints for the storage nodes.
|
||||||
WARNING: DO NOT CHANGE THIS SETTING WITH ATTACHED VOLUMES.'
|
All Longhorn volumes should be detached before modifying toleration settings.
|
||||||
|
We recommend setting tolerations during Longhorn deployment because the Longhorn system cannot be operated during the update.
|
||||||
|
Multiple tolerations can be set here, and these tolerations are separated by semicolon. For example:
|
||||||
|
* `key1=value1:NoSchedule; key2:NoExecute`
|
||||||
|
* `:` this toleration tolerates everything because an empty key with operator `Exists` matches all keys, values and effects
|
||||||
|
* `key1=value1:` this toleration has empty effect. It matches all effects with key `key1`
|
||||||
|
Because `kubernetes.io` is used as the key of all Kubernetes default tolerations, it should not be used in the toleration settings.
|
||||||
|
WARNING: DO NOT CHANGE THIS SETTING WITH ATTACHED VOLUMES!"
|
||||||
group: "Longhorn Default Settings"
|
group: "Longhorn Default Settings"
|
||||||
type: string
|
type: string
|
||||||
default: ""
|
default: ""
|
||||||
|
Loading…
Reference in New Issue
Block a user