Skip to content
This repository has been archived by the owner on Apr 30, 2020. It is now read-only.

Operator deploys gluster-block #16

Open
3 tasks
JohnStrunk opened this issue Jun 26, 2018 · 0 comments
Open
3 tasks

Operator deploys gluster-block #16

JohnStrunk opened this issue Jun 26, 2018 · 0 comments
Labels
epic Large, multi-issue feature set needs-subtasks Issue needs to be sub-divided into smaller items

Comments

@JohnStrunk
Copy link
Member

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.

@JohnStrunk JohnStrunk added epic Large, multi-issue feature set needs-subtasks Issue needs to be sub-divided into smaller items labels Jun 26, 2018
@JohnStrunk JohnStrunk added this to the 0.9 milestone Jun 26, 2018
@JohnStrunk JohnStrunk removed this from the 0.9 milestone Sep 24, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
epic Large, multi-issue feature set needs-subtasks Issue needs to be sub-divided into smaller items
Projects
None yet
Development

No branches or pull requests

1 participant