kubernetes/plugin
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
..
cmd/kube-scheduler Add version info to kube-scheduler, kube-proxy and kubelet logs. 2017-09-21 17:46:24 +08:00
pkg Fixed counting of unbound PVCs towards limit of attached volumes. 2017-10-02 15:49:34 +02:00
BUILD Update generated files - api, bazel, json 2017-09-04 09:02:35 +02:00
OWNERS Updated top level owners file to match new format 2017-01-19 11:29:16 -08:00