-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
node selection #17
Comments
scheduling to a specific node is easy spec:
nodeName: foo-node # schedule pod to specific node labelled nodes too spec:
nodeSelector:
disktype: ssd #this is the whole label |
as for affinity, this is a little more complicated required: spec:
affinity:
nodeAffinity:
requiredDuringSchedulingIgnoredDuringExecution:
nodeSelectorTerms:
- matchExpressions: preferred: spec:
affinity:
nodeAffinity:
preferredDuringSchedulingIgnoredDuringExecution:
- weight: 1
preference:
matchExpressions: match expressions are always the same format - key: another-node-label-key
operator: In
values:
- another-node-label-value operators are defined here: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#operators Topology spread will not be done with this feature, I'll add a new one |
additionally, |
so, one way would be for short syntax: deployment:
node: "name" long syntax: deployment:
node:
'label' : "value" affinity could be done like this: deployment:
affinity:
pod:
node: still thinking about how to do the rest and how to avoid the duplicate |
Awesome, thanks. Now it remains that I fill in the remaining blanks for antiAffinity I guess. |
a way to select a cluster node would be nice.
https://kubernetes.io/docs/tasks/configure-pod-container/assign-pods-nodes/
could work like this and support direct nodename as well as labeled nodes
for a labelled node:
The text was updated successfully, but these errors were encountered: