Skip to content

Conversation

azych
Copy link
Contributor

@azych azych commented Jan 30, 2025

Enables OCP to collect Prometheus metrics for both catalogd and operator-controller by default. This is accomplished via ServiceMonitor CRs which are now created for both projects.

Tested on both 4.19 and 4.19-nightly (aka main) versions:

Screenshot 2025-02-03 at 09 57 23 Screenshot 2025-02-03 at 09 57 34 Screenshot 2025-02-03 at 09 57 44

Fixes OCPBUGS-49410

Copy link
Contributor

openshift-ci bot commented Jan 30, 2025

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jan 30, 2025
@azych azych force-pushed the enable-metrics-collection-by-default branch 3 times, most recently from 82a5757 to 80839da Compare January 30, 2025 11:27
@azych azych changed the title [WIP] Enable OCP metrics collection for catalogd [WIP] Enable OCP metrics collection by default Jan 30, 2025
@azych azych changed the title [WIP] Enable OCP metrics collection by default [WIP] OCPBUGS-49410: Enable OCP metrics collection by default Jan 30, 2025
@openshift-ci-robot openshift-ci-robot added jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Jan 30, 2025
@openshift-ci-robot
Copy link

@azych: This pull request references Jira Issue OCPBUGS-49410, which is invalid:

  • expected the bug to target the "4.19.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

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 openshift-eng/jira-lifecycle-plugin repository.

Copy link
Member

@joelanford joelanford left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Two things:

  1. We should do a similar thing for operator-controller
  2. We'll need these included in the kustomize directory somewhere. The manifests directories are generated from kustomize.

@azych
Copy link
Contributor Author

azych commented Jan 30, 2025

Two things:

1. We should do a similar thing for operator-controller

yes, I intend to, it's a Draft-WIP at this point until I can verify that everything is working and come up with manifests for operator-controller

2. We'll need these included in the kustomize directory somewhere. The manifests directories are generated from kustomize.

good point, I'll do that before removing Draft-WIP status of this PR

@tmshort
Copy link
Contributor

tmshort commented Jan 30, 2025

Fundamentally, these files are supposed to be created through the kustomize mechanism, which means adding resources to the openshift/catalogd/kustomize/overlays/openshift directory and appropriate kustomization.yaml updates and patches.

@azych
Copy link
Contributor Author

azych commented Jan 31, 2025

Fundamentally, these files are supposed to be created through the kustomize mechanism, which means adding resources to the openshift/catalogd/kustomize/overlays/openshift directory and appropriate kustomization.yaml updates and patches.

good point, I'll do that before removing Draft-WIP status of this PR

@azych
Copy link
Contributor Author

azych commented Jan 31, 2025

@camilamacedo86 @joelanford @tmshort

To clarify & try to find the way forward:

@azych azych force-pushed the enable-metrics-collection-by-default branch from 80839da to c81e1e0 Compare January 31, 2025 09:32
@azych
Copy link
Contributor Author

azych commented Jan 31, 2025

/test all

@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jan 31, 2025
@azych azych force-pushed the enable-metrics-collection-by-default branch 2 times, most recently from 8924ee8 to a6a7e96 Compare February 3, 2025 08:53
@openshift-merge-robot openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Feb 3, 2025
@openshift-ci-robot
Copy link

@azych: No Jira issue is referenced in the title of this pull request.
To reference a jira issue, add 'XYZ-NNN:' to the title of this pull request and request another refresh with /jira refresh.

In response to this:

Enables OCP to collect Prometheus metrics for both catalogd and operator-controller by default. This is accomplished via ServiceMonitor CRs which are now created for both projects.

Tested on both 4.19 and 4.19-nightly (aka main) versions:

Screenshot 2025-02-03 at 09 57 23 Screenshot 2025-02-03 at 09 57 34 Screenshot 2025-02-03 at 09 57 44

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 openshift-eng/jira-lifecycle-plugin repository.

@azych azych changed the title UPSTREAM: <carry>: Enable OCP metrics collection by default UPSTREAM: <carry>: OCPBUGS-49410: Enable OCP metrics collection by default Feb 10, 2025
@openshift-ci-robot openshift-ci-robot added jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Feb 10, 2025
@openshift-ci-robot
Copy link

@azych: This pull request references Jira Issue OCPBUGS-49410, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.19.0) matches configured target version for branch (4.19.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @Xia-Zhao-rh

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

Enables OCP to collect Prometheus metrics for both catalogd and operator-controller by default. This is accomplished via ServiceMonitor CRs which are now created for both projects.

Tested on both 4.19 and 4.19-nightly (aka main) versions:

Screenshot 2025-02-03 at 09 57 23 Screenshot 2025-02-03 at 09 57 34 Screenshot 2025-02-03 at 09 57 44

Fixes OCPBUGS-49410

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 openshift-eng/jira-lifecycle-plugin repository.

@azych azych force-pushed the enable-metrics-collection-by-default branch from 1521ec4 to 982bfc3 Compare February 10, 2025 12:31
@tmshort
Copy link
Contributor

tmshort commented Feb 14, 2025

@azych this likely needs to be rebased.

@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Feb 14, 2025
Enables OCP to collect Prometheus metrics for both catalogd and
operator-controller by default. This is accomplished
via ServiceMonitor CRs which are now created for both projects.
@azych azych force-pushed the enable-metrics-collection-by-default branch from 982bfc3 to 77f9d42 Compare February 14, 2025 13:21
@openshift-merge-robot openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Feb 14, 2025
@tmshort
Copy link
Contributor

tmshort commented Feb 14, 2025

/approve
/lgtm
Looks as though @joelanford's requested changes might block merging.

@openshift-ci openshift-ci bot added lgtm Indicates that a PR is ready to be merged. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Feb 14, 2025
Copy link
Contributor

@camilamacedo86 camilamacedo86 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure how or where we can add E2E tests that won’t conflict with the bumper and are valid only for downstream OCP.

@dtfranz @tmshort might have a better idea on how to approach this. I’d also like to assess whether implementing this downstream-only test is worthwhile. If maintaining such a test exclusively downstream proves too difficult, then:

  • a) It might not be worth the effort

OR

  • b) It could still be valuable as a small E2E test—serving as an example or a foundation for expanding test coverage in the future.

What test we could add here?

Example: Check that the ServiceMonitor was created with success

Otherwise, I'm fine with it. So, /lgtm.

c/c @joelanford

@tmshort
Copy link
Contributor

tmshort commented Feb 14, 2025

Yeah, I noticed no tests... the best place might be part of the origin tests:
https://github.com/openshift/origin

@Xia-Zhao-rh
Copy link

/label qe-approved

@openshift-ci openshift-ci bot added the qe-approved Signifies that QE has signed off on this PR label Feb 17, 2025
Copy link
Contributor

openshift-ci bot commented Feb 17, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: azych, joelanford, tmshort

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

@azych
Copy link
Contributor Author

azych commented Feb 17, 2025

+1 I'll be following up with a test in https://github.com/openshift/origin once merged

@joelanford
Copy link
Member

/label acknowledge-critical-fixes-only

@openshift-ci openshift-ci bot added the acknowledge-critical-fixes-only Indicates if the issuer of the label is OK with the policy. label Feb 17, 2025
Copy link
Contributor

openshift-ci bot commented Feb 18, 2025

@azych: 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-sigs/prow repository. I understand the commands that are listed here.

@openshift-merge-bot openshift-merge-bot bot merged commit beab335 into openshift:main Feb 18, 2025
9 checks passed
@openshift-ci-robot
Copy link

@azych: Jira Issue OCPBUGS-49410: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-49410 has been moved to the MODIFIED state.

In response to this:

Enables OCP to collect Prometheus metrics for both catalogd and operator-controller by default. This is accomplished via ServiceMonitor CRs which are now created for both projects.

Tested on both 4.19 and 4.19-nightly (aka main) versions:

Screenshot 2025-02-03 at 09 57 23 Screenshot 2025-02-03 at 09 57 34 Screenshot 2025-02-03 at 09 57 44

Fixes OCPBUGS-49410

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-bot
Copy link

[ART PR BUILD NOTIFIER]

Distgit: ose-olm-catalogd
This PR has been included in build ose-olm-catalogd-container-v4.19.0-202502180408.p0.gbeab335.assembly.stream.el9.
All builds following this will include this PR.

@openshift-bot
Copy link

[ART PR BUILD NOTIFIER]

Distgit: ose-olm-operator-controller
This PR has been included in build ose-olm-operator-controller-container-v4.19.0-202502180408.p0.gbeab335.assembly.stream.el9.
All builds following this will include this PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
acknowledge-critical-fixes-only Indicates if the issuer of the label is OK with the policy. approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. qe-approved Signifies that QE has signed off on this PR
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants