Leela Gangavarapu

> If we don't support over-provisioning then we should call update_free_size() both during creation and during expansion. - as commented in the PR, I believe this should be fix, i.e,...

- I see kadalu already exports `kadalu_pvc_(total|used|free)_capacity_bytes`? @gerethd did you try using them? @vatsa287 do you mean anything else?

- ack, if possible would you be able to share any feedback for improvement?

- long answer https://github.com/kadalu/rfcs/blob/main/text/0007-Using-GlusterFS-directory-quota-for-external-gluster-volumes.adoc - short answer, it's one of external gluster nodes ssh privkey - maybe, it's better to expand the info in the doc, will take a look.

Hi @XuanTram did you get a chance to go through the RFC? If something that's mentioner in the RFC can be improved or doesn't sound right, pls let us know.

- In short, SSH has two parts, private and public keypair - Public key resides on one (or all) of external gluster nodes - You'll create secret in kadalu ns...

- Should reside on the host that you mention in kadalu CR

@deba10106 you'd just be creating CR for every gluster volume. For supplying multiple hosts, it's simply an yaml array with field `gluster_hosts`

- Just taking a quick look at the ask, do you have any approximate estimate that might go into maintaining this if developed?

> already is a part of volume 5f796784-bc1b-11ee-a19d-ae3c1976d0e5 - bricks weren't cleaned properly, pls force cleanup the backend path before reusing it or else use `volume_id: 5f796784-bc1b-11ee-a19d-ae3c1976d0e5` in `KadaluStorage` CR...