dntosas 6b51169005 Fix buckets initialization ... This metrics is measured in seconds so it makes no sense starting from 1000 as init value. This breaks also the scheduler e2e metric thus make users unable to compute, for example, their SLO for the scheduler. Even if this metric is deprecated, it should behave correctly until it is completely removed to avoid user confusion. For example, for each volume created, the minimum value exposed as a metric is 16.6min (1000sec/60) which is obviously wrong as logic. In this commit, we migrate bucket creation to start from reasonable numbers, copying the incrementation from the conventions that the scheduler follows itself. Signed-off-by: dntosas <ntosas@gmail.com>		2021-08-23 11:55:33 +03:00
..
metrics	Fix buckets initialization	2021-08-23 11:55:33 +03:00
BUILD	CSIStorageCapacity: check for sufficient storage in volume binder	2020-07-06 19:20:10 +02:00
OWNERS	Create OWNERS in volume scheduling package	2019-05-04 16:46:12 +08:00
scheduler_assume_cache.go	cleanup in volume scheduling pkg	2020-07-01 15:01:10 +08:00
scheduler_assume_cache_test.go	Fix pkg/controller typos in some error messages, comments etc	2020-02-27 00:15:33 +09:00
scheduler_binder.go	report UnschedulableAndUnresolvable status instead of an error when PVCs can't find bound persistent volumes	2020-11-06 09:53:50 +08:00
scheduler_binder_fake.go	Share pod volume binding cache via framework.CycleState	2020-06-23 22:18:33 +08:00
scheduler_binder_test.go	report UnschedulableAndUnresolvable status instead of an error when PVCs can't find bound persistent volumes	2020-11-06 09:53:50 +08:00