Loading...

XML

Word

Printable

Release Note Status:
In Progress
Release Note Type:
Bug Fix
Release Note Text:

Hide
Cordoned nodes filtered from alerts to reduce false positives::
Before this update, the `KubeNodeNotReady` and `KubeNodeReadinessFlapping` alerts did not filter out cordoned nodes. As a consequence, users received alerts for nodes under maintenance, resulting in false positives. With this release, cordoned nodes are filtered from alerts. As a result, the number of false positives during maintenance is reduced.
+
link:https://issues.redhat.com/browse/OCPBUGS-60692[OCPBUGS-60692]

Show
Cordoned nodes filtered from alerts to reduce false positives:: Before this update, the `KubeNodeNotReady` and `KubeNodeReadinessFlapping` alerts did not filter out cordoned nodes. As a consequence, users received alerts for nodes under maintenance, resulting in false positives. With this release, cordoned nodes are filtered from alerts. As a result, the number of false positives during maintenance is reduced. + link: https://issues.redhat.com/browse/OCPBUGS-60692 [ OCPBUGS-60692 ]

Description of problem:

    I believe filtering out cordoned nodes from the alert would help curb false positives for nodes which are undergoing maintenance.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:

    1.
    2.
    3.

Actual results:

Expected results:

Additional info:

    Original Patch: https://github.com/kubernetes-monitoring/kubernetes-mixin/pull/1012

clones

OCPBUGS-60692 Filter NodeReadiness to take cordoned nodes into account

depends on

OCPBUGS-35095 `KubeCPUOvercommit` Alert Not Triggered Despite Node CPU is Overcommitment

links to