Add recommended node practices for CNV environments
This commit adds recommendations based on chaos testing:
- Guidance to avoid extended VMs downtime during node outages.
- Guidance on Node Health Check and Self Node Remediation/FAR remediation mechanisms - setup, tunings and recovery timing based on the VMs load.
- Capacity planning guidance to support VMs migration when remediations are enabled during node outages.
🤖 Mon Nov 18 19:20:40 - Prow CI generated the docs preview:
https://84095--ocpdocs-pr.netlify.app/
Hi @jcanocan, made the changes suggested, need your review when you get time please. Thanks!
Thanks for the review @jcanocan! Updated the PR as per your suggestions. Need your review when you get time please.
@chaitanyaenr: 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-sigs/prow repository. I understand the commands that are listed here.
Please reject the merge for OpenShift Virtualization. Instead, open a Jira ticket at https://issues.redhat.com/secure/CreateIssueDetails!init.jspa?pid=12323181&issuetype=1&components=12333768&priority=10200&summary=%5BDoc%5D&customfield_12316142
Please reject the merge for OpenShift Virtualization. Instead, open a Jira ticket at https://issues.redhat.com/secure/CreateIssueDetails!init.jspa?pid=12323181&issuetype=1&components=12333768&priority=10200&summary=%5BDoc%5D&customfield_12316142
Hi @ctomasko Thanks for the pointers, created a Jira ticket to add/maintain the recommendations for every supported release: https://issues.redhat.com/browse/CNV-52129. Please feel free to let us know in case of any questions. Looking forward to collaborating on it. Thanks.
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
Stale issues rot after 30d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle rotten /remove-lifecycle stale
Rotten issues close after 30d of inactivity.
Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.
/close
@openshift-bot: Closed this PR.
In response to this:
Rotten issues close after 30d of inactivity.
Reopen the issue by commenting
/reopen. Mark the issue as fresh by commenting/remove-lifecycle rotten. Exclude this issue from closing again by commenting/lifecycle frozen./close
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.