From 6ffedc3bded7e4dfdc4d696c87a16942c0353cbf Mon Sep 17 00:00:00 2001 From: "W. Trevor King" Date: Tue, 5 Nov 2019 16:29:05 -0800 Subject: [PATCH] config/v1/types_cluster_operator: Fix "Degraded indicated" -> "Degraded indicates" And drop the earlier, orphaned comment block. Both of these issues slipped through my earlier 40c55f8085 (config/v1/types_cluster_operator: ClusterOperatorStatus doc wordsmithing, 2019-10-28, #501). --- config/v1/types_cluster_operator.go | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/config/v1/types_cluster_operator.go b/config/v1/types_cluster_operator.go index 46783f9733e..a57b76a123b 100644 --- a/config/v1/types_cluster_operator.go +++ b/config/v1/types_cluster_operator.go @@ -149,11 +149,7 @@ const ( // a previously known state. OperatorProgressing ClusterStatusConditionType = "Progressing" - // Degraded indicates that the operand is not functioning completely. An example of a degraded state - // would be if there should be 5 copies of the operand running but only 4 are running. It may still be available, - // but it is degraded - - // Degraded indicated that the operator's current state does not match its + // Degraded indicates that the operator's current state does not match its // desired state over a period of time resulting in a lower quality of service. // The period of time may vary by component, but a Degraded state represents // persistent observation of a condition. As a result, a component should not