-
Notifications
You must be signed in to change notification settings - Fork 42k
Update prometheus client golang #127941
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
Update prometheus client golang #127941
Conversation
|
Skipping CI for Draft Pull Request. |
|
This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the The DetailsInstructions 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-sigs/prow repository. |
|
Sigh! on prometheus/client_golang@bccd682 |
@dims, what issues did this commit introduce? It's my mess, and I would like to know more to prevent it from happening again in the future. |
Ok, I see the dependency changes. We will do a better job next time and maybe even remove dependencies. |
|
Yea, we can adjust and learn here (e.g. remove a dep) |
@kakkoyun thank you! you are right, it's the dependencies. When k8s generates all the staging libraries and people use them in the wild, we are passing on these dependencies to them.
So we are very very conscious of what we pick up both for ourselves (things that end up in our binaries) but also our libraries that we pass along to our consumers. |
@bwplotka thank you! very much appreciate all the work you all do! |
|
PR needs rebase. DetailsInstructions 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-sigs/prow repository. |
logicalhan
left a comment
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
/approve
|
/hold Discussed at sig-instrumentation, and consensus was that we want to explore if a revert of the change in client_golang is possible. @logicalhan @dgrisonnet |
|
/remove-sig api-machinery |
|
/lgtm cancel The changes to the SIG Auth tests (encryption at rest and authenticator) looks unexpected. Please tag @kubernetes/sig-auth-pr-reviews for review after resolving the merge conflicts and #127941 (comment) is resolved. |
|
Proposed a revert, we will make a decision tomorrow: prometheus/client_golang#1645 Thanks and apologies for the pain here! |
|
The problematic change was reverted: https://github.com/prometheus/client_golang/releases/tag/v1.20.5 |
|
Closing for now. If needed, i'll open a new PR. |
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
Update prometheus/client_golang and adapt to behavioral change to the prometheus testutil library.
Special notes for your reviewer:
Changes to prometheus tests are is due to prometheus/client_golang#1424. Prior to that change, the metrics were used only as a filter. The test would not fail if a metric in the list was not present. After the change, including a metric that was not present in the exposition would fail the test.
Does this PR introduce a user-facing change?