mirror of
https://github.com/kubernetes/kubernetes.git
synced 2026-06-09 08:55:55 -04:00
5686664a1d
Normally, the PV controller knows about the PVC that triggers the creation of a PV before it sees the PV, because the PV controller must set the volume.beta.kubernetes.io/storage-provisioner annotation that tells an external provisioner to create the PV. When restarting, the PV controller first syncs its caches, so that case is also covered. However, the creator of a PVC might decided to set that annotation itself to speed up volume creation. While unusual, it's not forbidden and thus part of the external Kubernetes API. Whether it makes sense depends on the intentions of the user. When that is done and there is heavy load, an external provisioner might see the PVC and create a PV before the PV controller sees the PVC. If the PV controller then encounters the PV before the PVC, it incorrectly concludes that the PV needs to be deleted instead of being bound. The same issue occurred earlier for external binding and the existing code for looking up a PVC in the cache or in the apiserver solves the issue also for volume provisioning, it just needs to be enabled also for PVs without the pv.kubernetes.io/bound-by-controller annotation. |
||
|---|---|---|
| .. | ||
| config | ||
| metrics | ||
| options | ||
| testing | ||
| util | ||
| binder_test.go | ||
| BUILD | ||
| delete_test.go | ||
| framework_test.go | ||
| index.go | ||
| index_test.go | ||
| OWNERS | ||
| provision_test.go | ||
| pv_controller.go | ||
| pv_controller_base.go | ||
| pv_controller_test.go | ||
| recycle_test.go | ||
| volume_host.go | ||