Michael Tinsley
07/13/2023, 2:10 PMinterruptible=True
)? And if not, is this something that would be considered?
My justification is this - currently with nodeSelector, it can easily make a task unschedulable, for example we do not run GPUs on Spot nodes so a GPU task with interruptible=True
will never be schedulable. By using nodeAffinity instead of nodeSelector, this behaviour can be configured by the user with either requiredDuringSchedulingIgnoredDuringExecution
or preferredDuringSchedulingIgnoredDuringExecution
Rahul Mehta
07/13/2023, 4:59 PMnodeAffinity
as well.Michael Tinsley
07/13/2023, 5:01 PMRahul Mehta
07/13/2023, 9:40 PMOlivier Sevin
10/02/2023, 9:23 PMspec.containers[*].image
, spec.initContainers[*].image
, spec.activeDeadlineSeconds
, `spec.tolerations`" .Rahul Mehta
10/02/2023, 9:24 PMOlivier Sevin
10/02/2023, 9:24 PMRahul Mehta
10/02/2023, 9:24 PMPodTemplate
- so we still have the separation of concerns between pipeline authors and lower-level infra details / they're separated by codeowners in our monorepo, but unfortunately we couldn't fully handle this on the cluster sidePodTemplate
seems much more functional than the previous hand-rolled PodTask we'd written, and you can specify a full podspec properly there (including nodeAffinity terms, podAntiAffinity, etc)