Skip to content

Latest commit

 

History

History
14 lines (10 loc) · 2.62 KB

V1TopologySpreadConstraint.md

File metadata and controls

14 lines (10 loc) · 2.62 KB

V1TopologySpreadConstraint

TopologySpreadConstraint specifies how to spread matching pods among the given topology.

Properties

Name Type Description Notes
label_selector V1LabelSelector [optional]
max_skew int MaxSkew describes the degree to which pods may be unevenly distributed. When `whenUnsatisfiable=DoNotSchedule`, it is the maximum permitted difference between the number of matching pods in the target topology and the global minimum. For example, in a 3-zone cluster, MaxSkew is set to 1, and pods with the same labelSelector spread as 1/1/0: zone1
topology_key str TopologyKey is the key of node labels. Nodes that have a label with this key and identical values are considered to be in the same topology. We consider each <key, value> as a &quot;bucket&quot;, and try to put balanced number of pods into each bucket. It's a required field.
when_unsatisfiable str WhenUnsatisfiable indicates how to deal with a pod if it doesn't satisfy the spread constraint. - DoNotSchedule (default) tells the scheduler not to schedule it. - ScheduleAnyway tells the scheduler to schedule the pod in any location, but giving higher precedence to topologies that would help reduce the skew. A constraint is considered &quot;Unsatisfiable&quot; for an incoming pod if and only if every possible node assigment for that pod would violate &quot;MaxSkew&quot; on some topology. For example, in a 3-zone cluster, MaxSkew is set to 1, and pods with the same labelSelector spread as 3/1/1: zone1

[Back to Model list] [Back to API list] [Back to README]