Hi Vishnu,
Thanks for your patience, after looking into this we’ve concluded the current documentation is correct which states Glusterfs is supported, but not gluster-block. The reason for this is because gluster-block cannot be used to reliably recover Pods if kubernetes decides to schedule them on a different node since " gluster-block volumes can only be mounted by one node/client at a time" (using glustefs).
While it’s true that gluster-block seems to be more compatible with couchbase itself when it comes to displaying available storage, this will also be true for glusterfs as we address these issues in couchbase 6.5, and in our testing we’ve verified that the actual usage of glusterfs does in fact work with the couchbase Pods aside from this one issue which doesn’t have any impact on usage of cluster itself.