Deduplicate PVC usage alerts across nodes

[weirdwiz]

PersistentVolumeUsage alerts were firing once per node for RWX volumes because kubelet on each node reports volume stats independently and Prometheus adds a node label during scraping. For RWX volumes mounted on N nodes, this created N identical alerts. The fix deduplicates across nodes while keeping only namespace/PVC labels.

[openshift-cherrypick-robot]

@weirdwiz: once the present PR merges, I will cherry-pick it on top of release-4.21 in a new PR and assign it to you.

In response to this:

/cherry-pick release-4.21

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.

[weirdwiz]

/cherry-pick release-4.20

[weirdwiz]

/cherry-pick release-4.19

[weirdwiz]

/cherry-pick release-4.18

[openshift-cherrypick-robot]

@weirdwiz: once the present PR merges, I will cherry-pick it on top of release-4.20 in a new PR and assign it to you.

In response to this:

/cherry-pick release-4.20

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.

[openshift-cherrypick-robot]

@weirdwiz: once the present PR merges, I will cherry-pick it on top of release-4.19 in a new PR and assign it to you.

In response to this:

/cherry-pick release-4.19

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.

[weirdwiz]

/cherry-pick release-4.17

[weirdwiz]

/cherry-pick release-4.16

[openshift-cherrypick-robot]

@weirdwiz: once the present PR merges, I will cherry-pick it on top of release-4.18 in a new PR and assign it to you.

In response to this:

/cherry-pick release-4.18

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.

[openshift-cherrypick-robot]

@weirdwiz: once the present PR merges, I will cherry-pick it on top of release-4.17 in a new PR and assign it to you.

In response to this:

/cherry-pick release-4.17

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.

[weirdwiz]

/cherry-pick release-4.15

[openshift-cherrypick-robot]

@weirdwiz: once the present PR merges, I will cherry-pick it on top of release-4.16 in a new PR and assign it to you.

In response to this:

/cherry-pick release-4.16

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.

[openshift-cherrypick-robot]

@weirdwiz: once the present PR merges, I will cherry-pick it on top of release-4.15 in a new PR and assign it to you.

In response to this:

/cherry-pick release-4.15

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.

[openshift-ci-robot]

@weirdwiz: The following backport issues have been created:

Queuing cherrypicks to the requested branches to be created after this PR merges:
/cherrypick release-4.20
/cherrypick release-4.19
/cherrypick release-4.18
/cherrypick release-4.17
/cherrypick release-4.16
/cherrypick release-4.15

In response to this:

/jira backport release-4.20,release-4.19,release-4.18,release-4.17,release-4.16,release-4.15

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-cherrypick-robot]

@openshift-ci-robot: once the present PR merges, I will cherry-pick it on top of release-4.15, release-4.16, release-4.17, release-4.18, release-4.19, release-4.20 in new PRs and assign them to you.

In response to this:

@weirdwiz: The following backport issues have been created:

Queuing cherrypicks to the requested branches to be created after this PR merges:
/cherrypick release-4.20
/cherrypick release-4.19
/cherrypick release-4.18
/cherrypick release-4.17
/cherrypick release-4.16
/cherrypick release-4.15

In response to this:

/jira backport release-4.20,release-4.19,release-4.18,release-4.17,release-4.16,release-4.15

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.

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.

[openshift-ci-robot]

@weirdwiz: This pull request references [Jira Issue DFBUGS-4531](https://issues.redhat.com//browse/DFBUGS-4531), which is invalid:

• expected the bug to target the "odf-4.20" 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.

In response to this:

PersistentVolumeUsage alerts were firing once per node for RWX volumes because kubelet on each node reports volume stats independently and Prometheus adds a node label during scraping. For RWX volumes mounted on N nodes, this created N identical alerts. The fix deduplicates across nodes while keeping only namespace/PVC labels.

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.

[Madhu-1]

/assign @iamniting @malayparida2000 for approval

[openshift-ci]

@Madhu-1: GitHub didn't allow me to assign the following users: for, approval.

Note that only red-hat-storage members with read permissions, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

In response to this:

/assign @iamniting @malayparida2000 for approval

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.

[Madhu-1]

/retitle Deduplicate PVC usage alerts across nodes

[openshift-ci-robot]

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

PersistentVolumeUsage alerts were firing once per node for RWX volumes because kubelet on each node reports volume stats independently and Prometheus adds a node label during scraping. For RWX volumes mounted on N nodes, this created N identical alerts. The fix deduplicates across nodes while keeping only namespace/PVC labels.

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]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: iamniting, Madhu-1, weirdwiz

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:

• OWNERS [iamniting]

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

[openshift-cherrypick-robot]

@weirdwiz: new pull request created: #3578

In response to this:

/cherry-pick release-4.17

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.

[openshift-cherrypick-robot]

@weirdwiz: #3577 failed to apply on top of branch "release-4.16":

Applying: Deduplicate PVC usage alerts across nodes
Using index info to reconstruct a base tree...
M	controllers/storagecluster/prometheus/localcephrules.yaml
Falling back to patching base and 3-way merge...
Auto-merging controllers/storagecluster/prometheus/localcephrules.yaml
CONFLICT (content): Merge conflict in controllers/storagecluster/prometheus/localcephrules.yaml
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0001 Deduplicate PVC usage alerts across nodes

In response to this:

/cherry-pick release-4.16

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.

[openshift-cherrypick-robot]

@weirdwiz: #3577 failed to apply on top of branch "release-4.15":

Applying: Deduplicate PVC usage alerts across nodes
Using index info to reconstruct a base tree...
M	controllers/storagecluster/prometheus/localcephrules.yaml
Falling back to patching base and 3-way merge...
Auto-merging controllers/storagecluster/prometheus/localcephrules.yaml
CONFLICT (content): Merge conflict in controllers/storagecluster/prometheus/localcephrules.yaml
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0001 Deduplicate PVC usage alerts across nodes

In response to this:

/cherry-pick release-4.15

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.

[openshift-cherrypick-robot]

@weirdwiz: new pull request created: #3579

In response to this:

/cherry-pick release-4.20

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.

[openshift-cherrypick-robot]

@weirdwiz: new pull request created: #3580

In response to this:

/cherry-pick release-4.19

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.

[openshift-cherrypick-robot]

@weirdwiz: new pull request created: #3581

In response to this:

/cherry-pick release-4.18

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.