Will the pv name be customizable?

[zjuliuf]

The pv name consists of prefix 'pvc-' and UID of the pending pvc currently. Will the pv name be customizable?

// getProvisionedVolumeNameForClaim returns PV.Name for the provisioned volume.
// The name must be unique.
func (ctrl *ProvisionController) getProvisionedVolumeNameForClaim(claim *v1.PersistentVolumeClaim) string {
return "pvc-" + string(claim.UID)
}

[zjuliuf]

Looking forward to getting your reply. Thanks a lot! @gnufied @mortent @Atoms @pohly

[niranjandarshann]

@zjuliuf Yes, the name of the persistent volume (PV) can be customized. By default, it consists of the prefix 'pvc-' followed by the unique identifier (UID) of the pending persistent volume claim (PVC).

[niranjandarshann]

However, you can specify a custom name for the PV when you create it manually. This involves creating a PV definition in a YAML file where you can define your desired name for the PV.

[zjuliuf]

@niranjandarshann Thank you for your reply. As you mentioned, we can specify a custom name for the PV only when we create it manually. Whether can we specify a custom name for the PV when the PV is created dynamically by volume provisioner?

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[jsafrane]

#178 has been merged recently, the next release will have a callback to provide a PV name.
/close