TAS: Better accuracy of scheduling by tighter integration with kube-scheduler

[mimowo]

What would you like to be added:

Improve accuracy of Topology-Aware Scheduling by respecting PodTemplate settings which are currently ignored by could block actual scheduling of pods at the kube-scheduler level. For example pod affinities and anti-affinities.

One option is tighter integration with kube-scheduler, similarly as ClusterAutoscaler does, however it may entail worse performance. Another option, is to gradually improve scheduling accuracy based on user feedback, but replicating the most commonly user properties (as currently we support tolerations).

Why is this needed:

TAS may currently schedule workloads which are unschedulable at the kube-scheduler level. Giving early feedback to users why such workloads cannot be scheduled would improve user experience.

Completion requirements:

This enhancement requires the following artifacts:

• Design doc
• API change
• Docs update

The artifacts should be linked in subsequent comments.

[mimowo]

cc @mwielgus @mwysokin @tenzen-y

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[tenzen-y]

/remove-lifecycle stale