Skip to content

MON-4115: expose label metrics for jobs and cronjobs#2553

Merged
openshift-merge-bot[bot] merged 2 commits into
openshift:mainfrom
rexagod:MON-4115
Apr 17, 2026
Merged

MON-4115: expose label metrics for jobs and cronjobs#2553
openshift-merge-bot[bot] merged 2 commits into
openshift:mainfrom
rexagod:MON-4115

Conversation

@rexagod
Copy link
Copy Markdown
Member

@rexagod rexagod commented Jan 8, 2025

Adds jobs and cronjobs to the exposed set of label metrics, i.e., --metric-labels-allowlist=pods=[*],nodes=[*],namespaces=[*],persistentvolumes=[*],persistentvolumeclaims=[*],poddisruptionbudgets=[*],jobs=[*],cronjobs=[*] by introducing a wrapper AdditionalResourceLabels field (see #2553 (comment) for details).

  • I added CHANGELOG entry for this change.
  • No user facing changes, so no entry in CHANGELOG was needed.

The linked issue is a feature request by a customer that requested these metrics to build their dashboards. I'm not sure what the qualifying factors were for the inclusion of the existing set of exposed label metrics --metric-labels-allowlist=pods=[*],nodes=[*],namespaces=[*],persistentvolumes=[*],persistentvolumeclaims=[*],poddisruptionbudgets=[*], but I'm assuming we do so when there's an explicit and reasonable request to expose them.

Nonetheless, I've opened this PR to set a ground for discussion if we want to incorporate this, or not.


TODO: Introduce this field in openshift/api#2778 once this is in.

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

openshift-ci-robot commented Jan 8, 2025

@rexagod: This pull request references MON-4115 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the feature request to target the "4.19.0" version, but no target version was set.

Details

In response to this:

Adds jobs and cronjobs to the exposed set of label metrics:

  • --metric-labels-allowlist=pods=[*],nodes=[*],namespaces=[*],persistentvolumes=[*],persistentvolumeclaims=[*],poddisruptionbudgets=[*],jobs=[*],cronjobs=[*]
  • I added CHANGELOG entry for this change.
  • No user facing changes, so no entry in CHANGELOG was needed.

The linked issue is a feature request by a customer that requested these metrics to build their dashboards. I'm not sure what the qualifying factors were for the inclusion of the existing set of exposed label metrics --metric-labels-allowlist=pods=[*],nodes=[*],namespaces=[*],persistentvolumes=[*],persistentvolumeclaims=[*],poddisruptionbudgets=[*], but I'm assuming we do so when there's an explicit and reasonable request to expose them.

Nonetheless, I've opened this PR to set a ground for discussion if we want to incorporate this, or not.

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-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jan 8, 2025
@openshift-ci openshift-ci Bot requested review from danielmellado and jan--f January 8, 2025 11:37
@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 8, 2025
@rexagod
Copy link
Copy Markdown
Member Author

rexagod commented Jan 8, 2025

/jira refresh

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

openshift-ci-robot commented Jan 8, 2025

@rexagod: This pull request references MON-4115 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the feature request to target the "4.19.0" version, but no target version was set.

Details

In response to this:

/jira refresh

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.

@rexagod
Copy link
Copy Markdown
Member Author

rexagod commented Jan 8, 2025

/jira refresh

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

openshift-ci-robot commented Jan 8, 2025

@rexagod: This pull request references MON-4115 which is a valid jira issue.

Details

In response to this:

/jira refresh

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.

@rexagod rexagod force-pushed the MON-4115 branch 3 times, most recently from c25eb30 to 7ad69ad Compare January 8, 2025 22:07
@juzhao
Copy link
Copy Markdown
Contributor

juzhao commented Jan 9, 2025

/retest-required

@rexagod
Copy link
Copy Markdown
Member Author

rexagod commented Jan 9, 2025

I'm having some issues running make generate on macOS, it's a gift that keeps giving.

@juzhao
Copy link
Copy Markdown
Contributor

juzhao commented Jan 26, 2025

/retest

@juzhao
Copy link
Copy Markdown
Contributor

juzhao commented Jan 29, 2025

/label qe-approved

@openshift-ci openshift-ci Bot added the qe-approved Signifies that QE has signed off on this PR label Jan 29, 2025
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

openshift-ci-robot commented Jan 29, 2025

@rexagod: This pull request references MON-4115 which is a valid jira issue.

Details

In response to this:

Adds jobs and cronjobs to the exposed set of label metrics:

  • --metric-labels-allowlist=pods=[*],nodes=[*],namespaces=[*],persistentvolumes=[*],persistentvolumeclaims=[*],poddisruptionbudgets=[*],jobs=[*],cronjobs=[*]
  • I added CHANGELOG entry for this change.
  • No user facing changes, so no entry in CHANGELOG was needed.

The linked issue is a feature request by a customer that requested these metrics to build their dashboards. I'm not sure what the qualifying factors were for the inclusion of the existing set of exposed label metrics --metric-labels-allowlist=pods=[*],nodes=[*],namespaces=[*],persistentvolumes=[*],persistentvolumeclaims=[*],poddisruptionbudgets=[*], but I'm assuming we do so when there's an explicit and reasonable request to expose them.

Nonetheless, I've opened this PR to set a ground for discussion if we want to incorporate this, or not.

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.

@machine424
Copy link
Copy Markdown
Contributor

left a comment on the ticket.

@rexagod
Copy link
Copy Markdown
Member Author

rexagod commented Apr 10, 2025

[from the f2f] @machine424 suggested we have the default allowlist, in addition to a set of "allowed" resources that the users could choose to enable from. The allowlist itself will thus be customizable from CMO's config.

@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Apr 10, 2025
@openshift-merge-robot openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jul 8, 2025
@rexagod
Copy link
Copy Markdown
Member Author

rexagod commented Jul 8, 2025

Support extending the labels-allowlist based on this discussion.

Comment thread go.mod Outdated
Comment thread pkg/manifests/manifests.go Outdated
@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Sep 16, 2025
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

openshift-ci-robot commented Apr 2, 2026

@rexagod: This pull request references MON-4115 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the feature request to target either version "4.22." or "openshift-4.22.", but it targets "openshift-5.0" instead.

Details

In response to this:

Adds jobs and cronjobs to the exposed set of label metrics, i.e., --metric-labels-allowlist=pods=[*],nodes=[*],namespaces=[*],persistentvolumes=[*],persistentvolumeclaims=[*],poddisruptionbudgets=[*],jobs=[*],cronjobs=[*] by introducing a wrapper AdditionalResourceLabels field (see #2553 (comment) for details).

  • I added CHANGELOG entry for this change.
  • No user facing changes, so no entry in CHANGELOG was needed.

The linked issue is a feature request by a customer that requested these metrics to build their dashboards. I'm not sure what the qualifying factors were for the inclusion of the existing set of exposed label metrics --metric-labels-allowlist=pods=[*],nodes=[*],namespaces=[*],persistentvolumes=[*],persistentvolumeclaims=[*],poddisruptionbudgets=[*], but I'm assuming we do so when there's an explicit and reasonable request to expose them.

Nonetheless, I've opened this PR to set a ground for discussion if we want to incorporate this, or not.


TODO: Introduce this field in openshift/api#2778 once this is in.

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.

@rexagod
Copy link
Copy Markdown
Member Author

rexagod commented Apr 2, 2026

/jira refresh

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

openshift-ci-robot commented Apr 2, 2026

@rexagod: This pull request references MON-4115 which is a valid jira issue.

Details

In response to this:

/jira refresh

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
Copy Markdown
Contributor

@simonpasquier simonpasquier left a comment

Choose a reason for hiding this comment

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

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Apr 2, 2026
@simonpasquier
Copy link
Copy Markdown
Contributor

/test e2e-aws-ovn-techpreview

1 similar comment
@simonpasquier
Copy link
Copy Markdown
Contributor

/test e2e-aws-ovn-techpreview

@rexagod
Copy link
Copy Markdown
Member Author

rexagod commented Apr 7, 2026

/verified by tests

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Apr 7, 2026
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@rexagod: This PR has been marked as verified by tests.

Details

In response to this:

/verified by tests

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-merge-bot
Copy link
Copy Markdown
Contributor

/retest-required

Remaining retests: 0 against base HEAD 2e2c0aa and 2 for PR HEAD 3c57aca in total

@openshift-merge-bot
Copy link
Copy Markdown
Contributor

/retest-required

Remaining retests: 0 against base HEAD f6a7969 and 1 for PR HEAD 3c57aca in total

@rexagod
Copy link
Copy Markdown
Member Author

rexagod commented Apr 9, 2026

/test e2e-aws-ovn-techpreview

@openshift-merge-bot
Copy link
Copy Markdown
Contributor

/retest-required

Remaining retests: 0 against base HEAD 1f129c5 and 0 for PR HEAD 3c57aca in total

@openshift-merge-bot
Copy link
Copy Markdown
Contributor

/hold

Revision 3c57aca was retested 3 times: holding

@openshift-ci openshift-ci Bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Apr 13, 2026
@rexagod
Copy link
Copy Markdown
Member Author

rexagod commented Apr 14, 2026

/unhold
/test e2e-hypershift-conformance

Failures do not seem to stem from this PR.

@openshift-ci openshift-ci Bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Apr 14, 2026
@openshift-merge-bot
Copy link
Copy Markdown
Contributor

/retest-required

Remaining retests: 0 against base HEAD 1f129c5 and 2 for PR HEAD 3c57aca in total

@simonpasquier
Copy link
Copy Markdown
Contributor

/test e2e-hypershift-conformance

1 similar comment
@simonpasquier
Copy link
Copy Markdown
Contributor

/test e2e-hypershift-conformance

@openshift-merge-bot
Copy link
Copy Markdown
Contributor

/retest-required

Remaining retests: 0 against base HEAD d14a276 and 1 for PR HEAD 3c57aca in total

@openshift-merge-bot
Copy link
Copy Markdown
Contributor

/retest-required

Remaining retests: 0 against base HEAD 88f9787 and 0 for PR HEAD 3c57aca in total

@simonpasquier
Copy link
Copy Markdown
Contributor

simonpasquier commented Apr 17, 2026

comment deleted because wrong PR

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Apr 17, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: rexagod, simonpasquier

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:
  • OWNERS [rexagod,simonpasquier]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Apr 17, 2026

@rexagod: all tests passed!

Full PR test history. Your PR dashboard.

Details

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 5b0c9fd into openshift:main Apr 17, 2026
22 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

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. lgtm Indicates that a PR is ready to be merged. qe-approved Signifies that QE has signed off on this PR verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants