Sync CNV runbook KubeVirtVMGuestMemoryPressure.md (Updated at 2025-09-15 08:41:07 +0000 UTC)

[hco-bot]

This is an automated PR by 'tools/openshift-virtualization-operator/runbook-sync'.

CNV runbook 'KubeVirtVMGuestMemoryPressure.md' was updated in upstream https://github.com/kubevirt/monitoring at 2025-09-15 08:41:07 +0000 UTC.
This PR syncs the runbook in this repository to contain all new added changes.

/cc @machadovilaca @sradco @avlitman @jherrman

This pull request has been closed in favor of a newer one. Please refer to the updated PR for the latest changes and discussion: #376.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: hco-bot
Once this PR has been reviewed and has the lgtm label, please assign machadovilaca for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• alerts/openshift-virtualization-operator/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci]

Hi @hco-bot. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

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-sigs/prow repository.

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[sradco]

/remove-lifecycle stale