-
Notifications
You must be signed in to change notification settings - Fork 65
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
registration-service: new Service for metrics #1050
Conversation
new k8s Service to scrape the HTTP metrics from the registration service, but without exposing them to the current Route (the metrics will be exposed in a separate port in the registration service pods) see codeready-toolchain/registration-service#436 Signed-off-by: Xavier Coulon <[email protected]>
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: xcoulon 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 |
- kind: Service | ||
apiVersion: v1 | ||
metadata: | ||
name: api | ||
name: registration-service |
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 reordered the Routes and Services and added a few comments, but unfortunately, the diff
doesn't clearly shows how the items were reordered :/
closing in favor of #1051 (duplicate branch name) |
Related to codeready-toolchain/registration-service#436 New tests to verify that: 1. the metrics are _not_ exposed on the public Route 2. the expected metrics are available from the new Service[1] - tested from the outside of the cluster by creating a temporary Route [1]: see codeready-toolchain/host-operator#1050 Signed-off-by: Xavier Coulon <[email protected]>
Related to codeready-toolchain/registration-service#436 New tests to verify that: 1. the metrics are _not_ exposed on the public Route 2. the expected metrics are available from the new Service[1] - tested from the outside of the cluster by creating a temporary Route [1]: see codeready-toolchain/host-operator#1050 --------- Signed-off-by: Xavier Coulon <[email protected]> Co-authored-by: Alexey Kazakov <[email protected]>
new k8s Service to scrape the HTTP metrics from the registration
service, but without exposing them to the current Route
(the metrics will be exposed in a separate port in the
registration service pods)
see codeready-toolchain/registration-service#436
Signed-off-by: Xavier Coulon [email protected]