-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
fix: .
is removed in nodeName
#2373
Conversation
.
is removed in nodeName.
is removed in nodeName
.
is removed in nodeName.
is removed in nodeName
This should fix #2374. Thank you, I hope this can get merged quickly! |
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. Alternatively, it looks like the ,
in the pattern
might have been a typo. We could just replace that with a .
.
/assign @dgrisonnet |
There was a conversation here: https://github.com/kubernetes/kube-state-metrics/pull/2217/files#r1356982673 https://github.com/kubernetes/kube-state-metrics/pull/2217/files#r1357024577 Do we still need this to differentiate between "" and nil? |
Good point. Updated to only add |
I read https://github.com/kubernetes/kube-state-metrics/pull/2217/files#r1356982673 https://github.com/kubernetes/kube-state-metrics/pull/2217/files#r1357024577 again and find it is not related to differentiate between "" and nil. |
Updated. Need review again. |
I don't get why we have this Also one thing I am curious about is what would happen once the pod is scheduled on the node. Do we continue to produce a stale metrics with the state of the pod when it wasn't schedule? Or do we have a mechanism to check that this pod shouldn't be watched by this shard anymore? |
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.
I approve - but I'm not sure that means anything. :)
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: CatherineF-dev, diranged, LaikaN57 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 |
No. I tested for both daemonset (watch scheduled pods) and deployment (watch not scheduled pods).
|
@dgrisonnet need review again. |
Closing this in favor of #2388 Feel free to reopoen if anything changes. |
What this PR does / why we need it:
How does this change affect the cardinality of KSM: (increases, decreases or does not change cardinality) No
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes # an issue raised in slack chat
We see the fieldSelector get created with the node-name … but it’s missing the .