mirror of https://github.com/k3s-io/k3s
![]() Automatic merge from submit-queue (batch tested with PRs 57252, 57168). If you want to cherry-pick this change to another branch, please follow the instructions <a href="https://github.com/kubernetes/community/blob/master/contributors/devel/cherry-picks.md">here</a>. Implementing predicates ordering **What this PR does / why we need it**: implements predicates ordering for the scheduler **Which issue(s) this PR fixes** : Fixes #53812 **Special notes for your reviewer**: @bsalamat @gmarek @resouer as discussed on slack, to implement ordering we have to choices: - use a layered approach with a list that indexes the order of the predicates map - change the underlying data structure used to represent a collection of predicates (a map in our case) into a list of predicates objects. Going with this solution might be "cleaner" but it will require a lot of changes and will increase the cost for accessing predicates from O(1) to O(n) (n being the number of predicates used by the scheduler). we might go with this solution for now. If the number of predicates start growing, we might switch to the second option. **Release note**: ```release-note adding predicates ordering for the kubernetes scheduler. ``` |
||
---|---|---|
.. | ||
cmd/kube-scheduler | ||
pkg | ||
BUILD | ||
OWNERS |