-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Regression in v0.20.2 #3144
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
Comments
For my understanding. You depend on us only exposing some of the Go runtime metrics? |
I'm okay to revert this for the patch releases, but I wouldn't revert it on main (aka for the next minor release) |
Reverting this is a breaking change as well for anyone who depends on this metric, so I am not in favor of that. Can you explain why you can not fix this on your end? |
Good point |
Actually sorry, I am just seeing we added this in a patch release, not a minor. I do agree we should revert this then |
Yeah that's what I was thinking 😅 I didn't see the potential for breaking anyone when backporting this |
Merged & released new patch releases /close |
@sbueringer: Closing this issue. In response to this:
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-sigs/prow repository. |
Maybe in the future, when upgrading to
ref: https://github.com/prometheus/client_golang/blob/main/prometheus/registry.go#L96-L134 |
Thx for adding that explanation @dongjiang1989 |
Hello, a regression was found in v0.20.2 caused by #3100
This breaks Cilium Operator initialization with the following error:
Is it possible to revert the PR? /cc @sbueringer
Thanks
The text was updated successfully, but these errors were encountered: