doc: remove deprecated predicates in scheduler
This commit is contained in:
parent
a46bdc27e1
commit
41b62a9305
|
@ -43,21 +43,6 @@ The following *predicates* implement filtering:
|
||||||
- `MaxCSIVolumeCount`: Decides how many {{< glossary_tooltip text="CSI" term_id="csi" >}}
|
- `MaxCSIVolumeCount`: Decides how many {{< glossary_tooltip text="CSI" term_id="csi" >}}
|
||||||
volumes should be attached, and whether that's over a configured limit.
|
volumes should be attached, and whether that's over a configured limit.
|
||||||
|
|
||||||
- `CheckNodeMemoryPressure`: If a Node is reporting memory pressure, and there's no
|
|
||||||
configured exception, the Pod won't be scheduled there.
|
|
||||||
|
|
||||||
- `CheckNodePIDPressure`: If a Node is reporting that process IDs are scarce, and
|
|
||||||
there's no configured exception, the Pod won't be scheduled there.
|
|
||||||
|
|
||||||
- `CheckNodeDiskPressure`: If a Node is reporting storage pressure (a filesystem that
|
|
||||||
is full or nearly full), and there's no configured exception, the Pod won't be
|
|
||||||
scheduled there.
|
|
||||||
|
|
||||||
- `CheckNodeCondition`: Nodes can report that they have a completely full filesystem,
|
|
||||||
that networking isn't available or that kubelet is otherwise not ready to run Pods.
|
|
||||||
If such a condition is set for a Node, and there's no configured exception, the Pod
|
|
||||||
won't be scheduled there.
|
|
||||||
|
|
||||||
- `PodToleratesNodeTaints`: checks if a Pod's {{< glossary_tooltip text="tolerations" term_id="toleration" >}}
|
- `PodToleratesNodeTaints`: checks if a Pod's {{< glossary_tooltip text="tolerations" term_id="toleration" >}}
|
||||||
can tolerate the Node's {{< glossary_tooltip text="taints" term_id="taint" >}}.
|
can tolerate the Node's {{< glossary_tooltip text="taints" term_id="taint" >}}.
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue