k3s/test/integration/scheduler
Davanum Srinivas 6cd8bd62fe
e2e test harness - use busybox from dockerhub
Use the same pattern everywhere in the e2e test
harness, use busybox (from dockerhub) instead
of using the one from k8s.gcr.io registry.

Change-Id: I57c3b867408c1f9478a8909c26744ea0368ff003
2018-08-07 11:22:16 -04:00
..
BUILD Merge pull request #65616 from cofyc/fix56163 2018-07-31 19:18:00 -07:00
OWNERS Updated OWNERS_ALIASES for scheduler, and added scheduler integration test owners. 2017-07-01 09:28:52 +08:00
extender_test.go update tests to be specific about the versions they are testing instead of floating 2018-05-01 13:18:41 -04:00
main_test.go use testmain in integration tests 2017-07-12 17:34:55 -07:00
predicates_test.go Do not schedule pod to the node under PID pressure. 2018-04-26 10:07:42 +08:00
preemption_test.go Fix PDB preemption tests. 2018-05-16 17:18:46 -07:00
priorities_test.go Add pod eviction logic for scheduler preemption 2017-09-07 15:31:55 -07:00
scheduler_test.go Move pkg/scheduler/schedulercache -> pkg/scheduler/cache 2018-05-31 22:55:34 +08:00
taint_test.go test(scheduler): add more integration tests for TaintNodesByCondition 2018-07-25 16:09:02 -07:00
util.go Merge pull request #65616 from cofyc/fix56163 2018-07-31 19:18:00 -07:00
volume_binding_test.go e2e test harness - use busybox from dockerhub 2018-08-07 11:22:16 -04:00