Preference/optional form of PodSpec.NodeSelector #8008
Labels
area/api
Indicates an issue on api area.
priority/backlog
Higher priority than priority/awaiting-more-evidence.
sig/scheduling
Categorizes an issue or PR as relevant to SIG Scheduling.
Borg has preferences a.k.a. "soft constraints." We should have the same thing in Kubernetes. (Try to place this pod on a node that satisfies this selector, but if you can't, schedule it anywhere else.) We could call it PodSpec.PreferredNodeSelector or something like that.
Sorry if this issue is already filed but I didn't immediately see it.
The text was updated successfully, but these errors were encountered: