Jan Safranek 2caae38d32 Fixed counting of unbound PVCs towards limit of attached volumes. ... There are two ways how a scheduled pod can get its PVCs unbound: - admin forcefuly unbinds it - user deletes original PVC that was bound when the pod was scheduled and creates a new one with the same name that does not get bound from some reason. In both cases we don't know where the original PVC pointed at and if we should account it to the limit of attached AWS EBS / GCE PDs etc. The common pattern here is to count it in when in doubt.		2017-10-02 15:49:34 +02:00
..
BUILD	Fixed counting of unbound PVCs towards limit of attached volumes.	2017-10-02 15:49:34 +02:00
error.go	Add specific errors for pod affinity predicates	2017-09-13 23:47:58 +08:00
metadata_test.go	Add pod eviction logic for scheduler preemption	2017-09-07 15:31:55 -07:00
metadata.go	Add pod eviction logic for scheduler preemption	2017-09-07 15:31:55 -07:00
predicates_test.go	Fixed counting of unbound PVCs towards limit of attached volumes.	2017-10-02 15:49:34 +02:00
predicates.go	Fixed counting of unbound PVCs towards limit of attached volumes.	2017-10-02 15:49:34 +02:00
utils_test.go	run hack/update-all	2017-06-22 11:31:03 -07:00
utils.go	Cover get equivalence cache in core	2017-08-03 23:03:52 +08:00