-
Notifications
You must be signed in to change notification settings - Fork 27
Bug 2115821: Fix controller metrics port #278
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
Conversation
@mrogers950: This pull request references Bugzilla bug 2115821, which is invalid:
Comment 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/test-infra repository. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: mrogers950 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 |
/bugzilla refresh |
@mrogers950: This pull request references Bugzilla bug 2115821, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker. 3 validation(s) were run on this bug
Requesting review from QA contact: 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/test-infra repository. |
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.
Looks like a reasonable change. Any idea how we can test this in CI?
We could add a test that curls against the endpoint to check that its running (we already CI test the custom metrics). But this would really be testing that controller-runtime started the default metrics listener. not sure that is too useful. |
Hm, the bundle jobs fail like:
|
/retest |
/bugzilla cc-qa |
/label qe-approved |
/test all |
/retest |
- Run the controller-runtime metrics (controller workload stats) on port 8383. - Remove the service endpoint for http-metrics. This was previously an additional metrics endpoint provided by operator-sdk, but was only useful for proxy programs. controller-runtime now only provides controller workqueue metrics. - Ensure the metrics service is updated on operator startup. In turn this will update the ServiceMonitor for new changes to the service endpoints.
/retest |
We're just referencing this here as related art, right? We don't have a CO specific bug, do we (I couldn't find one)? |
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
Just one question on bug tracking, otherwise this looks good.
@mrogers950: all tests passed! Full PR test history. Your PR dashboard. 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/test-infra repository. I understand the commands that are listed here. |
@mrogers950: All pull requests linked via external trackers have merged: Bugzilla bug 2115821 has been moved to the MODIFIED state. 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/test-infra repository. |
Bug: https://bugzilla.redhat.com/show_bug.cgi?id=2115821