Two ideas were suggested in that thread:

1. Run multiple schedulers, each with one policy configuration and each responsible for a disjoint set of pods
2. Run a single scheduler, which figures out which policies to apply for each pod it is scheduling

We haven't tried either of these, but you are definitely welcome to try it out and let us know if you have problems.

OK. I am going to try them and let you know if there is any progress/problem.

I have a similar issue. My first thought was multiple schedulers, then add to the podspec/rcspec to allow the pod to specify the scheduler to use for it. Resort to the default (with some warning message) if the desired scheduler isn't available. In my case, it may be viable to just allow multiple default scheduler instances, each with their own configuration file and name (label).

Please see #367 , but I'm all for multiple schedulers too ;-)

After a rough consideration, I would prefer to go for a single scheduler with multiple policies for specific pods. I am working on the codes and hope to show something sooner:)

Issues go stale after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Freeze the issue for 90d with /lifecycle frozen.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle stale

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle rotten
/remove-lifecycle stale

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close