-
Notifications
You must be signed in to change notification settings - Fork 40k
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
Adding metrics support to local volume #49598
Adding metrics support to local volume #49598
Conversation
Hi @sbezverk. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with 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. I understand the commands that are listed here. |
/assign @msau42 |
pkg/volume/local/local.go
Outdated
@@ -107,6 +107,7 @@ func (plugin *localVolumePlugin) NewMounter(spec *volume.Spec, pod *v1.Pod, _ vo | |||
mounter: plugin.host.GetMounter(), | |||
plugin: plugin, | |||
globalPath: volumeSource.Path, | |||
MetricsProvider: volume.NewMetricsDu(volumeSource.Path), |
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.
what's the difference between NewMetricsDu and NewMetricsStatFS
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.
NewMetricsDu calculates the volume usage and device free space by executing "du", NewMetricsStatFS calculates the used and available space by stat'ing and gathering filesystem info for the Volume path.
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.
Hm I would use StatFS then since most of the other plugins use that, and it'll be more reliable than parsing output from a command.
/ok-to-test |
I think we'll need a release note since the metrics is user-visible. /release-note |
Also please open an issue for this and link it here |
/sig storage |
Fixes #49601 |
/test pull-kubernetes-e2e-gce-etcd3 |
/test pull-kubernetes-verify |
1 similar comment
/test pull-kubernetes-verify |
@sbezverk If you read the build log (clicking the details link beside the failed test) you'll note that this isn't a flake, but your PR is failing gofmt.
To fix, run |
Adding metrics support to local volume plugin
/lgtm |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: msau42, sbezverk No associated issue. Update pull-request body to add a reference to an issue, or get approval with The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these OWNERS Files:
You can indicate your approval by writing |
/test pull-kubernetes-e2e-gce-etcd3 |
4 similar comments
/test pull-kubernetes-e2e-gce-etcd3 |
/test pull-kubernetes-e2e-gce-etcd3 |
/test pull-kubernetes-e2e-gce-etcd3 |
/test pull-kubernetes-e2e-gce-etcd3 |
/retest |
/test pull-kubernetes-e2e-gce-etcd3 |
1 similar comment
/test pull-kubernetes-e2e-gce-etcd3 |
@fejta It keeps failing. Any suggestions to move forward with this PR? |
/test pull-kubernetes-e2e-gce-etcd3 |
/retest |
Automatic merge from submit-queue (batch tested with PRs 49619, 49598, 47267, 49597, 49638) |
Adding metrics support to local volume plugin.
Fixes #49601