Description of problem: KubePodCrashLooping is alerting on critical severity. As of current best practices this should be on a warning level instead since it's a cause based alert rather than a symptom based alert Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Cause a crashloop 2. 3. Actual results: `severity: critical` Expected results: `severity: warning` Additional info: this has been fixed upstream [1] already and needs to be implemented into cluster monitoring [1] https://github.com/kubernetes-monitoring/kubernetes-mixin/commit/050dedeba07b0ebd782beebef63f6c0168713ff3
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 (OpenShift Container Platform 4.6 GA Images), 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:4196