install/0000_90_cluster-version-operator_02_servicemonitor: Drop "unstable" from ClusterOperatorDegraded #369
Conversation
…table" from ClusterOperatorDegraded If we considered Degraded=True something that impacted update stability, I expect we'd want a guard against it that blocked new updates until admins coaxed the operator back into happiness. This commit softens wording from af62f04 (install: add alerts for cluster-version-operator, 2019-08-07, openshift#232).
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: wking The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
openshift-ci-robot
added
the
approved
|
And apparently I was wrong. While we don't consider Degraded=True sufficient to block update initialization, we do consider it sufficient to block manifest-graph application (except for installation). /close |
|
@wking: Closed this PR. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
3 participants
If we considered
Degraded=Truesomething that impacted update stability, I expect we'd want a guard against it that blocked new updates until admins coaxed the operator back into happiness. This commit softens wording from af62f04 (#232)./assign @abhinavdahiya