-
Notifications
You must be signed in to change notification settings - Fork 2k
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
feat: add kube_node_status_addresses metric #2252
feat: add kube_node_status_addresses metric #2252
Conversation
Welcome @stonith! |
59571c6
to
25bdd67
Compare
/assign @rexagod |
53445fc
to
10c7c9d
Compare
Seems to work as expected in a dualstack GKE cluster:
|
2524d4d
to
8497b03
Compare
I am not a fan of adding labels to the It would be better to have a dedicated @mrueg interested about your opinion on this |
Ah well I just saw #2252 (comment), I guess our opinion align then 😆 |
Yep, the kube_node_status_addresses would be my preference. Also I don't think prometheus allows to have the same label multiple times. Ideally it would look like this and we'll keep internal_ip still in there with a TODO to kill it in ksm-3.x
|
8497b03
to
0a9d3d2
Compare
Updated PR to add kube_node_status_address metric |
This looks good to me, two small requests:
|
0a9d3d2
to
f5cd4f8
Compare
|
f5cd4f8
to
069aeeb
Compare
added the missed |
/lgtm thanks! |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: mrueg, stonith The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What this PR does / why we need it:
Adds
kube_node_status_addresses
metric to account for mutiple addresses per type.How does this change affect the cardinality of KSM: (increases, decreases or does not change cardinality)
Adds a new metric per node