-
Notifications
You must be signed in to change notification settings - Fork 807
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
Volume metrics #524
Volume metrics #524
Conversation
Thanks for your pull request. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). 📝 Please follow instructions at https://git.k8s.io/community/CLA.md#the-contributor-license-agreement to sign the CLA. It may take a couple minutes for the CLA signature to be fully registered; after that, please reply here with a new comment and we'll verify. Thanks.
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
Welcome @Henni! |
Hi @Henni. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Pull Request Test Coverage Report for Build 1446
💛 - Coveralls |
/check-cla |
@Henni thx for the contribution! |
pkg/driver/statter.go
Outdated
inodesFree = int64(statfs.Ffree) | ||
inodesUsed = inodes - inodesFree | ||
return | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there a way we can reuse code from core k8s to do this rather than copying similar logic here? We can consider moving these utility functions somewhere common where all CSI drivers can use them.
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle stale A requirement achieving production grade? |
@Henni could you finish your work? This PR is really nice and would be very helpful in my job :) I saw in other drivers this functionality is successfully implemented. |
This issue is still on my list. I hope to get back to it next week. |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: Henni The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@Henni: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
Rebased and removed the statter.go cc @matthiaslee @AndyXiangLi |
fixed with #677 |
@Henni: PR needs rebase. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
rebases #421
fixes #223, #499
Is this a bug fix or adding new feature?
New Feature
What is this PR about? / Why do we need it?
Implementation of
NodeGetVolumeStats
to report volume metrics:kubelet_volume_stats_available_bytes
kubelet_volume_stats_capacity_bytes
kubelet_volume_stats_inodes
kubelet_volume_stats_inodes_free
kubelet_volume_stats_inodes_used
kubelet_volume_stats_used_bytes
What testing is done?
Linting is fine.
I wasn't able to fully run the tests yet. I believe this is because the tests only run properly on Linux.