Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Minor tweaks for OperatorConditionsUnhealthy.md #272

Merged
merged 1 commit into from
Nov 4, 2024
+5 −4
Merged

Minor tweaks for OperatorConditionsUnhealthy.md #272

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 5 additions & 4 deletions docs/runbooks/OperatorConditionsUnhealthy.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,12 +2,12 @@

## Meaning

This alert fires when the and operator conditions or its secondary resources
This alert triggers when the operator conditions or its secondary resources
are in an error or warning state.

## Impact

Resources maintained by the operator may not be functioning correctly.
Resources maintained by the operator might not be functioning correctly.

## Diagnosis

Expand All @@ -17,7 +17,7 @@ Check the operator conditions:
kubectl get <CR> <CR_OBJECT> -n <namespace> -o jsonpath='{.status.conditions}'
```

e.g.:
For example:

```bash
kubectl get HyperConverged kubevirt-hyperconverged -n kubevirt -o jsonpath='{.status.conditions}'
Expand All @@ -26,8 +26,9 @@ kubectl get HyperConverged kubevirt-hyperconverged -n kubevirt -o jsonpath='{.st
## Mitigation

Based on the information obtained during the diagnosis procedure, try to
identify the root cause within the operator or any of its secondary resources
identify the root cause within the operator or any of its secondary resources,
and resolve the issue.

<!--DS: If you cannot resolve the issue, log in to the
link:https://access.redhat.com[Customer Portal] and open a support case,
attaching the artifacts gathered during the diagnosis procedure.-->
Expand Down
Loading