-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
kubeletstatsreceiver: Sync available volume metadata from /pods endpoint #690
kubeletstatsreceiver: Sync available volume metadata from /pods endpoint #690
Conversation
Codecov Report
@@ Coverage Diff @@
## master #690 +/- ##
==========================================
+ Coverage 86.13% 86.20% +0.06%
==========================================
Files 207 207
Lines 11317 11365 +48
==========================================
+ Hits 9748 9797 +49
- Misses 1238 1239 +1
+ Partials 331 329 -2
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
988ba7c
to
e618ad7
Compare
) | ||
|
||
var supportedLabels = map[MetadataLabel]bool{ | ||
MetadataLabelContainerID: true, | ||
labelVolumeType: true, |
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.
shouldn't it be MetadataLabelVolumeType
?
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.
Fixed.
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.
LGTM
@bogdandrutu - this is ready to merge. Please do when you get a chance. |
Increase instance size for prior-go
Description: Optionally sync
k8s.volume.type
label with volume metric. This information is collected from the Pod spec exposed via/pods
endpoint only if the receiver is configured to do so (usingextra_metadata_labels
option).Currently, Persistent Volume Claim is synced as its own type. This will be updated in a subsequent PR so that metadata from the actual storage backing the claim is synced instead using the Kubernetes API.
Testing: Added tests.
Documentation: Updated README.