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
Describe the feature you'd like to have.
The repo should have a document describing:
the request flow for all CSI calls
how API endpoints are located for volume ops and mounting
What is the value to the end user? (why is it a priority?)
This is primarily for the benefit of new developers or those not familiar with the code. It will allow them to understand the motivation for the various Services used and how they permit the gluster servers to be located. This will be helpful for extending the existing driver, adding new drivers, and for troubleshooting.
How will we know we have a good solution? (acceptance criteria)
Each CSI call should be enumerated with the other entities that are contacted and the general request flow for servicing that type of request.
All Services, Deployments, and other kube objects that are recommended when deploying the CSI driver should be described with their purpose.
The text was updated successfully, but these errors were encountered:
Describe the feature you'd like to have.
The repo should have a document describing:
What is the value to the end user? (why is it a priority?)
This is primarily for the benefit of new developers or those not familiar with the code. It will allow them to understand the motivation for the various Services used and how they permit the gluster servers to be located. This will be helpful for extending the existing driver, adding new drivers, and for troubleshooting.
How will we know we have a good solution? (acceptance criteria)
The text was updated successfully, but these errors were encountered: