以上述範例來部署， Pod 會直接被指定到 k8slab-worker 此節點，透過 kubectl describe pod 就不會看到任何跟 scheduler 有關的事件
1 2 3 4 5 6 7
Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal Pulling 90s kubelet Pulling image "hwchiu/netutils" Normal Pulled 88s kubelet Successfully pulled image "hwchiu/netutils"in 1.582945894s (1.582973894s including waiting) Normal Created 88s kubelet Created container server Normal Started 88s kubelet Started container server
DESCRIPTION: If the affinity requirements specified by this field are not met at scheduling time, the pod will not be scheduled onto the node. If the affinity requirements specified by this field cease to be met at some point during pod execution (e.g. due to an update), the system may or may not try to eventually evict the pod from its node.
A node selector represents the union of the results of one or more label queries over a set of nodes; that is, it represents the OR of the selectors represented by the node selector terms.
FIELDS: nodeSelectorTerms <Object> -required- Required. A list of node selector terms. The terms are ORed.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
$ kubectl explain pod.spec.affinity.nodeAffinity.requiredDuringSchedulingIgnoredDuringExecution.nodeSelectorTerms KIND: Pod VERSION: v1
RESOURCE: nodeSelectorTerms <Object>
DESCRIPTION: Required. A list of node selector terms. The terms are ORed.
A null or empty node selector term matches no objects. The requirements of them are ANDed. The TopologySelectorTerm type implements a subset of the NodeSelectorTerm.
FIELDS: matchExpressions <Object> A list of node selector requirements by node's labels. matchFields <Object> A list of node selector requirements by node's fields.
values <string> An array of string values. If the operator is In or NotIn, the values array must be non-empty. If the operator is Exists or DoesNotExist, the values array must be empty. If the operator is Gt or Lt, the values array must have a single element, which will be interpreted as an integer. This array is replaced during a strategic merge patch.
DESCRIPTION: The scheduler will prefer to schedule pods to nodes that satisfy the affinity expressions specified by this field, but it may choose a node that violates one or more of the expressions. The node that is most preferred is the one with the greatest sum of weights, i.e. for each node that meets all of the scheduling requirements (resource request, requiredDuringScheduling affinity expressions, etc.), compute a sum by iterating through the elements of this field and adding "weight" to the sum if the node matches the corresponding matchExpressions; the node(s) with the highest sum are the most preferred.
An empty preferred scheduling term matches all objects with implicit weight 0 (i.e. it's a no-op). A null preferred scheduling term matches no objects (i.e. is also a no-op).
FIELDS: preference <Object> -required- A node selector term, associated with the corresponding weight.
weight <integer> -required- Weight associated with matching the corresponding nodeSelectorTerm, in the range 1-100.