mirror of https://github.com/k3s-io/k3s
![]() Automatic merge from submit-queue Add additional testing scenarios for compute resource requests=0 I was asked about the qos tier of a pod that specified `--requests=cpu=0,memory=0 --limits=cpu=100m,memory=1Gi` and in just investigating current behavior, realized we should have an explicit test case to ensure that 0 values are preserved in defaulting passes, and that this is still a burstable pod (but the lowest for that tier as it related to eviction) /cc @vishh |
||
---|---|---|
.. | ||
doc.go | ||
policy.go | ||
policy_test.go | ||
qos.go | ||
qos_test.go | ||
types.go |