Allow customization of driver name#182
Conversation
|
@JamesClonk, you must sign our contributor license agreement before your changes are merged. Click here to sign the agreement. If you are a VMware employee, read this for further instruction. |
|
@JamesClonk, we have received your signed contributor license agreement. The review is usually completed within a week, but may take longer under certain circumstances. Another comment will be added to the pull request to notify you when the merge can proceed. |
|
@JamesClonk, VMware has rejected your signed contributor license agreement. The merge can not proceed until the agreement has been resigned. Click here to resign the agreement. Reject reason:
|
|
@JamesClonk, we have received your signed contributor license agreement. The review is usually completed within a week, but may take longer under certain circumstances. Another comment will be added to the pull request to notify you when the merge can proceed. |
|
@JamesClonk, VMware has approved your signed contributor license agreement. |
Description
Adds new flag
driver-nameto main, to allow users to customize the driver and change its default from "named-disk.csi.cloud-director.vmware.com" to another value.The intention is that this way there could be multiple instances/deployments of cloud-director-named-disk-csi-driver deployed on the same Kubernetes cluster but with different CSIDriver names (and storage classes), configured for multiple different VDC's which host Kubernetes nodes.
Checklist
This change is