+++ This bug was initially created as a clone of Bug #1717632 +++
There are no alerts currently for when a cluster operator goes degraded or unavailable. We should have alerts for these.
We need to define how long is "bad" (5m?)
These should be back ported to 4.1.z so we can see them in telemetry and cluster administrators know what is happening. These are important alerts.
We should identify whether the console dashboard should also show these if they're firing (since they're pretty critical)
All associated PRs have merged, moving to MODIFIED.
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.