Files
dokku/plugins/scheduler-k3s/templates/longhorn.yaml
T
Jose Diaz-Gonzalez 2619c3db08 fix: ensure critical addons come up when the node is tainted
Rather than taint on `node-role.kubernetes.io/master=true:NoSchedule`, we check for `CriticalAddonsOnly=true:NoSchedule` and taint on that.
2024-01-23 03:00:27 -05:00

42 lines
793 B
YAML

defaultSettings:
taintToleration: "CriticalAddonsOnly=true:NoSchedule"
longhornManager:
tolerations:
- key: CriticalAddonsOnly
operator: Equal
value: "true"
effect: "NoSchedule"
longhornDriver:
tolerations:
- key: CriticalAddonsOnly
operator: Equal
value: "true"
effect: "NoSchedule"
longhornUI:
tolerations:
- key: CriticalAddonsOnly
operator: Equal
value: "true"
effect: "NoSchedule"
longhornConversionWebhook:
- key: CriticalAddonsOnly
operator: Equal
value: "true"
effect: "NoSchedule"
longhornAdmissionWebhook:
- key: CriticalAddonsOnly
operator: Equal
value: "true"
effect: "NoSchedule"
longhornRecoveryBackend:
- key: CriticalAddonsOnly
operator: Equal
value: "true"
effect: "NoSchedule"