You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What would you like to be added:
It would be great to consider supporting Taints and Tolerations with effect: PreferNoSchedule when flavor assigner and TAS assigns flavor to workloads.
Why is this needed:
Currently, we respect the Node Taints on ResourceFlavor Taints, and Node Taints on TopologyAwareScheduling as well.
But, we respect only NoSchedule and NoExecute effects and do not evaluate PreferNoSchedule in the following:
Completion requirements:
I guess that we can look at what kube-scheduler do for effect:PreferNoSchedule, and then introduce the similar mechanism to Kueue as commonize solution across Flavor (ResourceFlavor Taints) and TAS Node selection.
This enhancement requires the following artifacts:
Design doc
API change
Docs update
The artifacts should be linked in subsequent comments.
The text was updated successfully, but these errors were encountered:
What would you like to be added:
It would be great to consider supporting Taints and Tolerations with
effect: PreferNoSchedule
when flavor assigner and TAS assigns flavor to workloads.Why is this needed:
Currently, we respect the Node Taints on ResourceFlavor Taints, and Node Taints on TopologyAwareScheduling as well.
But, we respect only
NoSchedule
andNoExecute
effects and do not evaluatePreferNoSchedule
in the following:Basic FlavorAssigning:
kueue/pkg/scheduler/flavorassigner/flavorassigner.go
Lines 492 to 494 in c623953
TAS:
kueue/pkg/cache/tas_flavor_snapshot.go
Lines 499 to 501 in c623953
Completion requirements:
I guess that we can look at what kube-scheduler do for
effect:PreferNoSchedule
, and then introduce the similar mechanism to Kueue as commonize solution across Flavor (ResourceFlavor Taints) and TAS Node selection.This enhancement requires the following artifacts:
The artifacts should be linked in subsequent comments.
The text was updated successfully, but these errors were encountered: