Commit d93b545
committed
clusteroperator: Ignore EvaluationConditionsDetected condition
As per godoc of cluster operator type
```
EvaluationConditionsDetected is used to indicate the result of the detection
logic that was added to a component to evaluate the introduction of an
invasive change that could potentially result in highly visible alerts,
breakages or upgrade failures. You can concatenate multiple Reason using
the "::" delimiter if you need to evaluate the introduction of multiple changes.
```
which is not required in our usecase to check cluster operator
availability so ignoring that state. This will also fix the debug logs
of start command which have following message
```
DEBU Unexpected operator status for authentication: EvaluationConditionsDetected
DEBU Unexpected operator status for config-operator: EvaluationConditionsDetected
DEBU Unexpected operator status for console: EvaluationConditionsDetected
DEBU Unexpected operator status for etcd: EvaluationConditionsDetected
DEBU Unexpected operator status for ingress: EvaluationConditionsDetected
DEBU Unexpected operator status for kube-apiserver: EvaluationConditionsDetected
DEBU Unexpected operator status for kube-controller-manager: EvaluationConditionsDetected
DEBU Unexpected operator status for kube-scheduler: EvaluationConditionsDetected
DEBU Unexpected operator status for machine-config: EvaluationConditionsDetected
DEBU Unexpected operator status for openshift-apiserver: EvaluationConditionsDetected
DEBU Unexpected operator status for openshift-controller-manager: EvaluationConditionsDetected
```1 parent 54882f6 commit d93b545
1 file changed
+2
-0
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
128 | 128 | | |
129 | 129 | | |
130 | 130 | | |
| 131 | + | |
| 132 | + | |
131 | 133 | | |
132 | 134 | | |
133 | 135 | | |
| |||
0 commit comments