Take parameters from SC and give preference.
At present the parameters for provisioner has been taken from ENV which has to be changed and enabled for SC parameter list. The TODO in the csi driver commit
https://github.com/gluster/gluster-csi-driver/blob/master/pkg/glusterfs/controllerserver.go#L59 has to be enabled and given priority over ENV
@Madhu-1 I believe I explained this requirement clearly, if not let me know. I can share more details. If it was clear, please send a PR.
/assign @Madhu-1
I'm still unclear about what benefit this provides to the admin. The CSI driver version (Gluster client) needs to stay in sync with the Gluster container version (Gluster server).
The most straightforward way to accomplish that (automatically, in a scalable way) is by having 1 csi driver instance per Gluster cluster. Going that route, there is no need to repeat the cluster connection info in each StorageClass object. It can be provided to the driver once at startup.
@humblec could you better describe the user value of putting this info in the SC?
@JohnStrunk @humblec What's the definition of MVP 1.0 label? Is it equivalent to GCS 1.0? If so can you please retag it with GCS/1.0 based on if the work can get completed in 2 week's time?
This is not a priority for GCS 1.0.