You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
At present the parameters for provisioner has been taken from
ENV
which has to be changed and enabled for SC parameter list. TheTODO
in the csi driver commithttps://github.com/gluster/gluster-csi-driver/blob/master/pkg/glusterfs/controllerserver.go#L59 has to be enabled and given priority over
ENV
The text was updated successfully, but these errors were encountered: