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
{{ message }}
This repository has been archived by the owner on Apr 30, 2020. It is now read-only.
Describe the feature you'd like to have.
The operator should be able to deploy the infrastructure necessary to use gluster-block volumes.
What is the value to the end user? (why is it a priority?)
Gluster-block volumes are commonly used for metadata intensive workloads as well as metrics and logging. Given how common these workloads are, users should have access to gb volumes when deploying a Gluster cluster through the operator.
How will we know we have a good solution? (acceptance criteria)
Gluster-block can be enabled in a cluster by adjusting the cluster CR
Operator will deploy and manage the CSI driver for g-b
Operator will deploy and manage the g-b pods necessary for providing iSCSI targets
Work items
Gluster-block is represented in the cluster CR
Operator can deploy and upgrade g-b CSI driver
Operator can deploy and upgrade g-b target pods
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered:
Describe the feature you'd like to have.
The operator should be able to deploy the infrastructure necessary to use gluster-block volumes.
What is the value to the end user? (why is it a priority?)
Gluster-block volumes are commonly used for metadata intensive workloads as well as metrics and logging. Given how common these workloads are, users should have access to gb volumes when deploying a Gluster cluster through the operator.
How will we know we have a good solution? (acceptance criteria)
Work items
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: