-
Notifications
You must be signed in to change notification settings - Fork 96
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.
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
Deprecate cpu and memory exceeds alerts #172
Deprecate cpu and memory exceeds alerts #172
Conversation
1fca059
to
8434876
Compare
alerts/openshift-virtualization-operator/KubeVirtComponentExceedsRequestedCPU.md
Outdated
Show resolved
Hide resolved
alerts/openshift-virtualization-operator/KubeVirtComponentExceedsRequestedCPU.md
Outdated
Show resolved
Hide resolved
8434876
to
bf5626d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/approve
/lgtm |
@ctomasko please let me know who should review and update the run books at this point. Thanks. |
/hold until doc team will approve this. |
@sradco @avlitman I have 2 writers who are updating the runbooks for v4.16. We have not sync'd the upstream/dowstream yet, see epic https://issues.redhat.com/browse/CNV-36859. |
/unhold since doc is handling @sradco |
/unhold |
/hold |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @sradco, I'll be happy to provide doc review. Just one comment that applies to both files. Thanks!
If triggered, it may be safely ignored and silenced. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this the established text for a deprecated alert? If you're open to changing it, I think we can make it clearer by using minimalism principles.
-
I'd suggest using the active voice ("You can safely ignore or silence this alert") instead of the passive voice ("it may be safely ignored and silenced").
-
I'd remove "it does not indicate an actual issue" because it adds some confusion, IMO, and "safely" implies that it's a non-issue.
Suggestion:
This alert has been deprecated; it does not indicate an actual issue. | |
If triggered, it may be safely ignored and silenced. | |
This alert is deprecated. You can safely ignore or silence it. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed thank you! and sorry for late response
Deprecate the KubeVirtComponentExceedsRequestedCPU and KubeVirtComponentExceedsRequestedMemory alerts, which the user can't fix. Signed-off-by: avlitman <alitman@redhat.com>
bf5626d
to
79f4eef
Compare
Hi @ousleyp will appreciate if you can review again. |
@avlitman: all tests passed! Full PR test history. Your PR dashboard. 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. I understand the commands that are listed here. |
/lgtm |
/unhold |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: avlitman, orenc1, ousleyp, sradco The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Deprecate the KubeVirtComponentExceedsRequestedCPU and KubeVirtComponentExceedsRequestedMemory alerts, which the user can't fix.
jira-ticket: https://issues.redhat.com/browse/CNV-37900
Special notes for your reviewer: