Describe the feature you'd like to have.
The operator should properly deploy a given version of the CSI-based gluster file volume driver.
What is the value to the end user? (why is it a priority?)
The operator should be the single point of contact for ~users~ admins to manage a Gluster deployment. As such, starting the operator and creating the "cluster CR" should be everything needed to be up and running.
How will we know we have a good solution? (acceptance criteria)
The operator will properly deploy the specified version of the CSI file driver when the cluster CR is created
The operator will provide the driver with the CA key necessary to access the Gluster cluster
The operator will remove the CSI driver when the cluster CR is deleted
The operator will upgrade the CSI driver when the supplied image tag is changed in the cluster CR
Describe the feature you'd like to have. The operator should properly deploy a given version of the CSI-based gluster file volume driver.
What is the value to the end user? (why is it a priority?) The operator should be the single point of contact for ~users~ admins to manage a Gluster deployment. As such, starting the operator and creating the "cluster CR" should be everything needed to be up and running.
How will we know we have a good solution? (acceptance criteria)
Additional context This depends on having a CSI driver: https://github.com/gluster/gluster-csi-driver