Skip to content

Pull requests: openshift/cluster-monitoring-operator

New pull request New
26 Open 2,664 Closed
26 Open 2,664 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Reviews
Filter by reviews
No reviews Review required Approved review Changes requested
Assignee
Filter by who’s assigned
Assigned to nobody Loading
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Pull requests list

Add .coderabbit.yaml to reduce review noise approved Indicates a PR has been approved by an approver from all required OWNERS files. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. lgtm Indicates that a PR is ready to be merged.
#2845 opened Mar 10, 2026 by danielmellado Loading…
@marioferh
8
[release-4.20] OCPBUGS-74490: Include kube_pod_labels in minimal profile jira/severity-moderate Referenced Jira bug's severity is moderate 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. verified Signifies that the PR passed pre-merge verification criteria
#2844 opened Mar 10, 2026 by openshift-cherrypick-robot Loading…
@juzhao @openshift-cherrypick-robot
11
Add dashboard-kernel-stack-af-packet-standalone.yaml do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress.
#2843 opened Mar 9, 2026 by midu16 • Draft
6
OCPBUGS-77977: [release-4.20] ensure CMO and its operands pods have the app.kubernetes.io/part-of: openshift-monitoring label backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. 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.
#2842 opened Mar 9, 2026 by openshift-cherrypick-robot Loading…
@juzhao
8
MON-4479: use TLS profile to configure CMO server approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.
#2841 opened Mar 6, 2026 by simonpasquier Loading…
15
NO-JIRA: add metrics for the validating webhook approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.
#2838 opened Mar 4, 2026 by simonpasquier Loading…
6
MON-4532: Introduce telemetry-specific monitors only approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD.
#2821 opened Feb 24, 2026 by rexagod Loading…
6
MON-4517: Introduce missing minimal monitors with "full" CP metrics approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.
#2814 opened Feb 10, 2026 by rexagod Loading…
29
MON-4493: add MetricsServerConfig support to ClusterMonitoring CRD approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.
#2809 opened Feb 2, 2026 by marioferh Loading…
33
WIP: MON-4492 implement ClusterMonitoring CRD AlertmanagerConfig support approved Indicates a PR has been approved by an approver from all required OWNERS files. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress.
#2808 opened Jan 30, 2026 by marioferh Loading…
3
OCPBUGS-48578: chore(metrics-server): prefer control-plane nodes and tolerate their taints approved Indicates a PR has been approved by an approver from all required OWNERS files. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. jira/severity-moderate Referenced Jira bug's severity is moderate 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. verified Signifies that the PR passed pre-merge verification criteria
#2801 opened Jan 28, 2026 by machine424 Loading…
20
DONOTMERGE: Test cluster upgrade with missing amconfig secret approved Indicates a PR has been approved by an approver from all required OWNERS files.
#2798 opened Jan 27, 2026 by slashpai Loading…
2
MON-4469: Migrate service discovery to EndpointSlice globally approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.
#2792 opened Jan 20, 2026 by slashpai Loading…
8
OCPBUGS-70250: Manual pick networkpolicy to 4.21 approved Indicates a PR has been approved by an approver from all required OWNERS files. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. 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.
#2783 opened Dec 26, 2025 by juzhao Loading…
17
[bot] Update jsonnet dependencies do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command.
#2763 opened Dec 1, 2025 by openshift-monitoring-bot bot Loading…
3
MON-4442: Add AGENTS.md to CMO approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.
#2761 opened Nov 27, 2025 by danielmellado Loading…
44
MON-4386,MON-4387: telemetry Collection Profile approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.
#2694 opened Oct 5, 2025 by rexagod Loading…
5 of 6 tasks
76
MON-4361,MON-4380: Optional Monitoring Capability approved Indicates a PR has been approved by an approver from all required OWNERS files. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD.
#2675 opened Sep 18, 2025 by rexagod Loading…
1 of 2 tasks
34
[wip] MON-4321: Send telemetry via remote-write approved Indicates a PR has been approved by an approver from all required OWNERS files. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD.
#2643 opened Aug 13, 2025 by jan--f • Draft
2 tasks
21
MON-4163: Allow whitelisting KSM metrics approved Indicates a PR has been approved by an approver from all required OWNERS files. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD.
#2625 opened Jul 23, 2025 by rexagod • Draft
1 of 2 tasks
9
feat: Support OpenShift-specific topologies approved Indicates a PR has been approved by an approver from all required OWNERS files. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD.
#2622 opened Jul 21, 2025 by rexagod • Draft
5
OCPBUGS-54806: Add telemetry for user-defined networks 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. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
#2596 opened Apr 29, 2025 by danwinship Loading…
@jan--f
15
MON-4115: expose label metrics for jobs and cronjobs approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. qe-approved Signifies that QE has signed off on this PR
#2553 opened Jan 8, 2025 by rexagod Loading…
1 of 2 tasks
28
OCPBUGS-45895: allow reconciling existing Secrets approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/severity-moderate Referenced Jira bug's severity is moderate 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. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. qe-approved Signifies that QE has signed off on this PR
#2539 opened Dec 17, 2024 by rexagod Loading…
1 of 2 tasks
58
OCPBUGS-17113: Lazy updates for Prometheus approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/severity-moderate Referenced Jira bug's severity is moderate 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. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. qe-approved Signifies that QE has signed off on this PR
#2395 opened Jun 26, 2024 by rexagod Loading…
1 of 2 tasks
46
ProTip! Type g i on any issue or pull request to go back to the issue listing page.