# Why do we need Prebinding of Persistent Volumes to PersistentVolumeClaims? Is this a relic? **URL:** \ **Category:** General Discussions\ **Tags:** docs\ **Created:** [January 23, 2021, 10:07pm UTC](https://discuss.kubernetes.io/t/why-do-we-need-prebinding-of-persistent-volumes-to-persistentvolumeclaims-is-this-a-relic/14570 "2021-01-23T22:07:12Z")\ **Posts on this page:** 1\ **Page:** 1
**Author:** ![rjain21](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/rjain21/32/6778_2.png) [@rjain21](https://discuss.kubernetes.io/u/rjain21)\ **Post date:** [January 23, 2021, 10:07pm UTC](https://discuss.kubernetes.io/t/why-do-we-need-prebinding-of-persistent-volumes-to-persistentvolumeclaims-is-this-a-relic/14570/1 "2021-01-23T22:07:12Z")
Asking for help? Comment out what you need so we can get more information to help you! ### Cluster information: Kubernetes version: 1.20 Cloud being used: (put bare-metal if not on a public cloud) Installation method: Kubeadm Host OS: Ubuntu CNI and version: Kubectl create -f [https://docs.projectcalico.org/manifests/custom-resources.yaml](https://docs.projectcalico.org/manifests/custom-resources.yaml) kubectl create -f [https://docs.projectcalico.org/manifests/tigera-operator.yaml](https://docs.projectcalico.org/manifests/tigera-operator.yaml) CRI and version: containerd Maybe I am misunderstanding this. According to the official documentation, you can create a PersistentVolume with the intent to use it with specific PersistentVolumeClaims. To achieve this, one has to use “prebinding”. On the other hand, one can use selectors when creating a PVC to bind to a specific PV. Thus, no need for prebinding. If the intent of the feature-set is to allow the ability to use a specific storage backend, I am a little confused by the need for prebinding. Can someone please help what use case PV → PVC prebinding is even needed when PVC → PV binding can be controlled? Appreciate the help in advance.