-
Notifications
You must be signed in to change notification settings - Fork 17
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
SECURESIGN-842 | Operator's metrics are not consumed by OCP monitor #557
Conversation
35918ef
to
be9fa75
Compare
@osmman @bouskaJ Quick question, I have been thinking about this a bit, like with the ci we needed to install Prometheus prior to installing the operator so it has a definition of the service monitor type, will this cause an issue? I believe it will, as it would fail to install on clusters without an install of Prometheus. Instead should this be tied to the securesign resource, as in:
then if enabled create the service monitors, service etc ? |
be9fa75
to
1987996
Compare
/retest |
I think that at this moment we can live with it, for example a lot of operators depends on cert-manager to make their admission webhooks to work correctly. So unfortunatly right not it is prerequisity. Definatly it will be prefered to make it optional. /lgtm |
1987996
to
832521b
Compare
@osmman Can I get another /lgtm pls :) |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: JasonPowr, osmman 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 |
Testing
To test this, you just need to build and deploy the operator, you should see a new target being created under
Observe -> Targets
calledrhtas-operator-controller-manager-metrics-monitor
, you should then be able to query the metrics of the operator.