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
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: