Skip to content
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

Merged
merged 2 commits into from
Aug 21, 2024

Conversation

JasonPowr
Copy link
Contributor

Testing

To test this, you just need to build and deploy the operator, you should see a new target being created under Observe -> Targets called rhtas-operator-controller-manager-metrics-monitor, you should then be able to query the metrics of the operator.

@JasonPowr JasonPowr force-pushed the consuming-metrics-in-ocp branch from 35918ef to be9fa75 Compare August 16, 2024 13:04
@JasonPowr
Copy link
Contributor Author

@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:

spec:
  monitoring:
    enabled: true
  rekor:
    externalAccess:
    ......

then if enabled create the service monitors, service etc ?

@JasonPowr JasonPowr force-pushed the consuming-metrics-in-ocp branch from be9fa75 to 1987996 Compare August 20, 2024 15:51
@JasonPowr
Copy link
Contributor Author

/retest

@JasonPowr JasonPowr requested a review from osmman August 21, 2024 07:39
@osmman
Copy link
Contributor

osmman commented Aug 21, 2024

@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:

spec:
  monitoring:
    enabled: true
  rekor:
    externalAccess:
    ......

then if enabled create the service monitors, service etc ?

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

@JasonPowr
Copy link
Contributor Author

@osmman Can I get another /lgtm pls :)

@openshift-ci openshift-ci bot added the lgtm label Aug 21, 2024
Copy link

openshift-ci bot commented Aug 21, 2024

[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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-merge-bot openshift-merge-bot bot merged commit d869458 into main Aug 21, 2024
13 of 14 checks passed
@osmman osmman deleted the consuming-metrics-in-ocp branch September 17, 2024 12:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants