While assessing 4.1.0 GA degraded operators Adam suggested capturing the reason (which has bounded cardinality) on the telemetry metric for cluster_operator_conditions, which would
1. incentivize teams to add good reasons
2. allow a quick summarization of why the operator is degraded
Added in https://github.com/openshift/cluster-version-operator/pull/197, should be back ported to 4.1.1
Created attachment 1586914 [details]
all 4.1 ClusterOperator info
Bug 1717619 is about 4.1.z. This bug and https://github.com/openshift/cluster-version-operator/pull/197 is about 4.2.0. I'm fixing the target release and pushing back to ON_QA to get double-checking on a 4.2 nightly.
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.