kubernetes/test/e2e/scheduling
Mike Dame 07029c941a Remove Limits from scheduling e2e balanced pod resources
The purpose of the pod created by `createBalancedPodForNodes()` is to ensure
that all nodes have equal resource requests (as seen by the scheduler). This
prevents the default scheduling behavior (which attempts to balance resource requests)
from interfering with e2e's which test other priorities/score plugins.

Because the scheduler only worries about requests, specifying `Limits` in this pod
is unnecessary. In fact, if the calculated "balancing" limit is too low, it can cause
the balancing pod to never start due to OOMKill errors, leading to flakes and failures.
2021-04-21 15:58:00 -04:00
..
events.go test/e2e/framework:move functions to test/e2e/scheduling/ 2020-02-10 12:34:19 +08:00
framework.go remove unused funcs for e2e predicates 2020-12-12 09:43:01 +08:00
limit_range.go Deflake LimitRange e2e test 2020-08-07 17:22:35 -07:00
nvidia-gpus.go Use local daemonset manifest for installing Nvidia drivers 2020-07-18 21:01:00 -05:00
OWNERS Audit of test/* OWNERS files 2019-10-10 15:52:51 -05:00
predicates.go Skip PodTopologySpread tests in a single node cluster scenario 2021-03-11 12:32:09 +01:00
preemption.go validates basic preemption works|validates lower priority pod preemption by critical pod: allocate 4/5 instead of 2/3 2021-04-13 09:47:28 +02:00
priorities.go Remove Limits from scheduling e2e balanced pod resources 2021-04-21 15:58:00 -04:00
ubernetes_lite.go Tag Multi-AZ scheduling tests as serial 2021-03-18 10:31:03 -07:00