-
Notifications
You must be signed in to change notification settings - Fork 1.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
⚠️ metrics are now on by default #510
Conversation
A few more points that popped up during the conversation:
|
testenv pkg handles the testing control plane, it doesn't touch |
PTAL |
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.
some minor nits.
PTAL |
[APPROVALNOTIFIER] This PR is APPROVED Approval requirements bypassed by manually added approval. This pull-request has been approved by: mengqiy 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 |
@mengqiy We're getting testing failures because multiple processes are trying to bind port 8080. We replaced the test Manager's default Kubebuilder options with PR: kubernetes-sigs/cluster-api#1107 |
I added something in the GoDoc: https://github.com/kubernetes-sigs/controller-runtime/pull/510/files#diff-7d903b129bc883285ffc5068c39c00b0R139 |
Updated release notes and the description of this PR. |
Thank you! |
Controller-runtime metrics are now enabled by default since kubernetes-sigs/controller-runtime#510 was merged. To disable metrics, we must explicitly set the port to "0".
Controller-runtime metrics are now enabled by default since kubernetes-sigs/controller-runtime#510 was merged. To disable metrics, we must explicitly set the port to "0".
It can be turn off by setting
manager.Options{MetricsBindAddress: "0"}
. GoDoc.Note: If upgrading from controller-runtime v0.1.* to v0.2.0-beta.4+ and you have multiple controller tests, you may hit an error that these tests are racing to bind the same default 8080 port. And only one of them can succeed, others may fail. You may turn off the metrics in your tests in this case.