pod has unbound immediate PersistentVolumeClaims
fanux opened this issue · comments
no persistent volumes available for this claim and no storage class is set.
We recommend running with a dynamic volume provisioner, which is why we don't mention manually creating PVs. If you have a dynamic provisioner but it's not acting on the default Storage Class (or there is no default Storage Class), you can set storageClassName
in the dataVolumeClaimTemplate
.
If you don't have a dynamic volume provisioner, you can manually provision Persistent Volumes just like you would for any other PVC. The dataVolumeClaimTemplate
supports all the fields of a PVC Spec, so you can set it to select the manually-provisioned PVs.
OK, I got it, I think we should add some docs in Prerequisites.