Skip to content

Feature Request: Report disk usage for volumes from this driver #203

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
jacksontj opened this issue Nov 7, 2019 · 2 comments
Closed

Feature Request: Report disk usage for volumes from this driver #203

jacksontj opened this issue Nov 7, 2019 · 2 comments

Comments

@jacksontj
Copy link

I was attempting to add some monitoring around my volume usage today and I found that I don't have them in my cluster. After some looking it appears that it is the responsibility of the csi driver to expose those metrics (google/cadvisor#1702 (comment)).

So assuming that is accurate (there are similar issues for other csi plugins, e.g. kubernetes-sigs/aws-ebs-csi-driver#223) -- then this is me requesting this be added to the digitalocean csi driver.

@timoreimann
Copy link
Contributor

timoreimann commented Nov 7, 2019

Hi there @jacksontj

You're right that CSI driver is responsible for providing (certain) metrics. Specifically, the gRPC endpoint NodeGetVolumeStats is supposed to provide data around disk and inode capacity.

I believe your request is a duplicate of #134. If you agree, then I'd like to close this issue.

The good news is that we have PR #197 in-flight right now that is going to ship support for the statistics endpoint described above. We are aiming for a new release of our CSI driver soon after that PR has merged. DOKS is planned to incorporate the CSI update on our next, internal release cycle.

Hope this helps.

@jacksontj
Copy link
Author

My apologies for missing that other issue, this definitely is a dupe. I'll go ahead and close this out

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants