-
Notifications
You must be signed in to change notification settings - Fork 31
UPSTREAM: <carry>: OCPBUGS-49410: Enable OCP metrics collection by default #252
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
UPSTREAM: <carry>: OCPBUGS-49410: Enable OCP metrics collection by default #252
Conversation
Skipping CI for Draft Pull Request. |
82a5757
to
80839da
Compare
@azych: This pull request references Jira Issue OCPBUGS-49410, which is invalid:
Comment 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. |
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.
Two things:
- We should do a similar thing for operator-controller
- We'll need these included in the kustomize directory somewhere. The manifests directories are generated from kustomize.
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
good point, I'll do that before removing Draft-WIP status of this PR |
Fundamentally, these files are supposed to be created through the kustomize mechanism, which means adding resources to the |
good point, I'll do that before removing Draft-WIP status of this PR |
@camilamacedo86 @joelanford @tmshort To clarify & try to find the way forward:
|
80839da
to
c81e1e0
Compare
...ft/catalogd/kustomize/overlays/openshift/olmv1-ns/metrics/catalogd_metrics_role_binding.yaml
Outdated
Show resolved
Hide resolved
openshift/catalogd/kustomize/overlays/openshift/olmv1-ns/metrics/catalogd_metrics_role.yaml
Show resolved
Hide resolved
openshift/catalogd/kustomize/overlays/openshift/olmv1-ns/metrics/catalogd_servicemonitor.yaml
Show resolved
Hide resolved
/test all |
openshift/catalogd/manifests/11-rolebinding-openshift-config-catalogd-manager-rolebinding.yml
Show resolved
Hide resolved
8924ee8
to
a6a7e96
Compare
@azych: No Jira issue is referenced in the title of this pull request. 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. |
@azych: This pull request references Jira Issue OCPBUGS-49410, which is valid. 3 validation(s) were run on this bug
Requesting review from QA contact: 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. |
1521ec4
to
982bfc3
Compare
@azych this likely needs to be rebased. |
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.
982bfc3
to
77f9d42
Compare
/approve |
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'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
Yeah, I noticed no tests... the best place might be part of the origin tests: |
/label qe-approved |
[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 |
+1 I'll be following up with a test in https://github.com/openshift/origin once merged |
/label acknowledge-critical-fixes-only |
@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. |
@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:
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. |
[ART PR BUILD NOTIFIER] Distgit: ose-olm-catalogd |
[ART PR BUILD NOTIFIER] Distgit: ose-olm-operator-controller |
Enables OCP to collect Prometheus metrics for both
catalogd
andoperator-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:
Fixes OCPBUGS-49410