Commit Graph

15 Commits

Author SHA1 Message Date
Daniel Kłobuszewski 2ee8023261 Don't break scale up with priority expander config 2022-10-11 10:52:02 +02:00
Benjamin Pineau 874cad0c79 Fix expanders unit tests
The github action hooks didn't run the unit tests on the expanders
update in #4233 (likely the known "tests don't run automatically for
new contributor" limitation).

NewStrategy became NewFilter, with a BestOptions (plural) method,
and returns a Options slice instead of a single Option.
2021-09-27 16:00:53 +02:00
Ryan McNamara 068af5bf7e Allow specification of multiple expanders
Multiple expanders can now be specified, expanders now "filter to the
tied for best" instead of "selecting the best" so the output of one
expander is now fed to the input of the next. Each expander may only
be used once to disallow bad configuration. This should not be a change
in functionality as in the event of a tie the random expander is still
used.
2021-09-23 14:31:39 -06:00
umialpha 8b9247e8e2 compare each priority, if not found, throw warning 2020-12-18 11:52:16 +08:00
umialpha 4d2fdb5d0d fix misleading log 2020-12-11 17:33:06 +08:00
Bartłomiej Wróblewski 0fb897b839 Update imports after scheduler scheduler/framework/v1alpha1 removal 2020-11-30 10:48:52 +00:00
Johannes Brück 734d48f4a2
Fix priority expander falling back to random although higher priority matches 2020-07-31 07:14:36 +02:00
Maciek Pytel 655b4081f4 Migrate to klog v2 2020-06-05 17:22:26 +02:00
Jakub Tużnik 73a5cdf928 Address recent breaking changes in scheduler
The following things changed in scheduler and needed to be fixed:
* NodeInfo was moved to schedulerframework
* Some fields on NodeInfo are now exposed directly instead of via getters
* NodeInfo.Pods is now a list of *schedulerframework.PodInfo, not *apiv1.Pod
* SharedLister and NodeInfoLister were moved to schedulerframework
* PodLister was removed
2020-04-24 17:54:47 +02:00
Mitchel Humpherys 0b7429a127 priority expander: Document skipping behavior for unmatched groups
If a group doesn't match any of the regexes in the priorities list it won't
be considered for expansion, which could catch some users off-guard.
Document this behavior.
2019-10-09 14:00:40 -07:00
Mitchel Humpherys 2e0d1f0b47 priority expander: Use kube-system namespace in example
CA is most often deployed in the kube-system namespace.  Modify the
ConfigMap example accordingly.
2019-10-09 13:59:59 -07:00
Mitchel Humpherys f671478808
priority expander: Document random fallback
When none of the regexes match in the priorities list,
CA will fall back to a random group selection.  Document
this in the readme.
2019-10-08 17:25:19 -07:00
Lukasz Piatkowski 856e58d599 rely on listers instead of watch api 2019-04-16 13:47:54 +02:00
Łukasz Osipiuk a331e1ce5d Disable failing priority expander tests 2019-04-12 14:34:05 +02:00
Lukasz Piatkowski c5ba4b3068 priority expander 2019-03-22 10:43:20 +01:00