A solution to https://bugzilla.redhat.com/show_bug.cgi?id=1743911 Description of problem: KubeAPILatencyHigh alert can be triggered when there is a long-running, resource-intensive job. A solution would be to apply https://prometheus.io/blog/2015/06/18/practical-anomaly-detection/ Version-Release number of selected component (if applicable): How reproducible: The resolution of the alert is very consistent and I can show data from specific clusters where resolution occurs within 10 minutes of the alert triggering. Steps to Reproduce: 1. Unknown 2. 3. Actual results: Expected results: Additional info:
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:0581