docs(gpu-operator): document tolerate-all on compat DaemonSet
Explain why tolerations: [{operator: Exists}] is safe on the driver
compat DaemonSet: the nodeSelector already confines scheduling to GPU
nodes, so the blanket toleration only kicks in when those nodes carry
the dedicated=gpu / nvidia.com/gpu taints that the GPU Operator's
default policy and many deployments apply.
Signed-off-by: Arsolitt <arsolitt@gmail.com>
This commit is contained in:
parent
5b210ac7fd
commit
4e37f64553
1 changed files with 7 additions and 0 deletions
|
|
@ -35,6 +35,13 @@ spec:
|
|||
# cluster uses to mark GPU hosts.
|
||||
nodeSelector:
|
||||
nvidia.com/gpu.present: "true"
|
||||
# Tolerate-all is intentionally broad: the nodeSelector above already
|
||||
# confines scheduling to GPU nodes, so the "Exists" toleration only
|
||||
# matters when those nodes carry extra taints (dedicated=gpu:NoSchedule,
|
||||
# nvidia.com/gpu:NoSchedule from the GPU Operator's default policy,
|
||||
# etc.). This mirrors the stance of the upstream nvidia-driver-daemonset
|
||||
# and nvidia-device-plugin DaemonSets — blanket tolerations plus a
|
||||
# narrow nodeSelector.
|
||||
tolerations:
|
||||
- operator: Exists
|
||||
initContainers:
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue