Drop the ClusterOperatorDown/Degraded alert tests

These turn out to be a duplication of tests that already flake if an operator does Available=false or Degraded=true in a test run. (i.e. [bz-DNS] clusteroperator/dns should not change condition/Degraded)

Author: dgoodwin

pkg/monitortestlibrary/allowedalerts/all.go

@@ -15,15 +15,6 @@ func AllAlertTests(jobType *platformidentification.JobType, etcdAllowance AlertT
 	ret = append(ret, newNamespacedAlert("KubePodNotReady", jobType).pending().neverFail().toTests()...)
 	ret = append(ret, newNamespacedAlert("KubePodNotReady", jobType).firing().toTests()...)
 
-	// ClusterOperatorDown and ClusterOperatorDegraded should not occur during a normal upgrade.
-	// In CI firing is rare, but does happen a few times a month. Pending however occurs all the time, which implies operators are routinely in
-	// a state they're not supposed to be during upgrade.
-	// https://github.com/openshift/enhancements/blob/cb81452fddf86c1099acd87610b88369cd6192db/dev-guide/cluster-version-operator/dev/clusteroperator.md#there-are-a-set-of-guarantees-components-are-expected-to-honor-in-return
-	ret = append(ret, newAlert("Cluster Version Operator", "ClusterOperatorDown", jobType).pending().alwaysFlake().toTests()...)
-	ret = append(ret, newAlert("Cluster Version Operator", "ClusterOperatorDegraded", jobType).pending().alwaysFlake().toTests()...)
-	ret = append(ret, newAlert("Cluster Version Operator", "ClusterOperatorDown", jobType).firing().alwaysFlake().toTests()...)
-	ret = append(ret, newAlert("Cluster Version Operator", "ClusterOperatorDegraded", jobType).firing().alwaysFlake().toTests()...)
-
 	ret = append(ret, newAlert("etcd", "etcdMembersDown", jobType).pending().neverFail().toTests()...)
 	ret = append(ret, newAlert("etcd", "etcdMembersDown", jobType).firing().toTests()...)
 	ret = append(ret, newAlert("etcd", "etcdGRPCRequestsSlow", jobType).pending().neverFail().toTests()...)