Michael Adam

started looking into this. As a preparation, here is a small improvement to the doc in question: #14167

First of all, such design discussions are imho better held in a PR with a design document than in issues, since the issues eventually scatter the content and decisions over...

Now for the design discussion: The old stack (heketi/gd1) has the high level block-volume management functionality in heketi, in parallel to the volume functionality. It is also using the volume...

@jarrpa that's a commit really, here's the more invariant branch: https://github.com/jarrpa/gluster-csi-driver/commits/heketi-support :-)

Having personal repos and mutually rebasing should also be good enough. It's common practice. Eventually stuff needs to land in the master branch in PRs anyway. So we can start...

@amarts I am not sure I fully understand the proposal: A gd1 based CSI driver would be using the heketi apis for high-level block volume provisioning with block hosting volume...

CAVEAT: needs to be tested

@atinmu this should roughly be what we discussed on chat today. Please take a look!

@humblec @nixpanic @jarrpa @SaravanaStorageNetwork @phlogistonjohn @raghavendra-talur @Madhu-1 ... what do you guys think?

@gobindadas @sac - I would like to hear your opinion about this idea :)