[OSDOCS-16009]: Adding evictionStrategy docs

[lahinson]

Version(s): OCP 4.17+

Issue: https://issues.redhat.com/browse/OSDOCS-16009

Link to docs preview: https://99578--ocpdocs-pr.netlify.app/openshift-enterprise/latest/hosted_control_planes/hcp-manage/hcp-manage-virt.html#hcp-virt-evict-vms_hcp-manage-virt

QE review:

• QE has approved this change.

Additional information: This update also needs to be applied to ACM 2.10 and ACM 2.11, which correspond with the OCP 4.15 and 4.16 docs

[ocpdocs-previewbot]

🤖 Fri Oct 10 16:12:44 - Prow CI generated the docs preview:

https://99578--ocpdocs-pr.netlify.app/openshift-enterprise/latest/hosted_control_planes/hcp-manage/hcp-manage-virt.html

[heliubj18]

/lgtm

[mgencur]

Just two minor issues. Otherwise looks good.

[openshift-ci]

New changes are detected. LGTM label has been removed.

[bergerhoffer]

/label merge-review-in-progress

[bergerhoffer]

The first steps seems pretty unnecessary (and a lot of text)- if there's something from there you want to share, you could explain it in the intro text.

But for the purposes of merge review, LGTM!

[lahinson]

@bergerhoffer Thanks for the review! I see your point about that first step.

@Skalador In the first step of this procedure, is the main purpose of running the following command to learn about the hyperconverged resource and the purpose of setting the evictionStrategy parameter?

$ oc explain hyperconverged.spec.evictionStrategy

If so, would it be okay to change the first step to something like, "To learn more about the hyperconverged resource and the allowed values for the evictionStrategy parameter, enter the following command:"

[Skalador]

@lahinson Yes it is to learn about the hyperconverged.spec.evictionStrategy options. Your proposal also is fine. Feel free to reduce the bloat of text with

"To learn more about the hyperconverged resource and the allowed values for the evictionStrategy parameter, enter the following command:"

[openshift-ci]

@lahinson: 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.

[lahinson]

/cherrypick enterprise-4.17

[lahinson]

/cherrypick enterprise-4.18

[lahinson]

/cherrypick enterprise-4.19

[lahinson]

/cherrypick enterprise-4.20

[openshift-cherrypick-robot]

@lahinson: #99578 failed to apply on top of branch "enterprise-4.17":

Applying: Adding evictionStrategy docs
.git/rebase-apply/patch:34: trailing whitespace.
In cases where KubeVirt virtual machines (VMs) cannot be live migrated, such as when you use GPU passthrough, the VMs must be evicted at the same time as the `NodePool` resource of the hosted cluster. Otherwise, the compute nodes might be shut down without being drained from the workload. This might also happen when you are upgrading the {VirtProductName} Operator. To achieve a synchronized restart, you can set the `evictionStrategy` parameter on the `hyperconverged` resource to ensure that only VMs that are drained from workloads are rebooted. 
warning: 1 line adds whitespace errors.
Using index info to reconstruct a base tree...
M	hosted_control_planes/hcp-manage/hcp-manage-virt.adoc
Falling back to patching base and 3-way merge...
Auto-merging hosted_control_planes/hcp-manage/hcp-manage-virt.adoc
CONFLICT (content): Merge conflict in hosted_control_planes/hcp-manage/hcp-manage-virt.adoc
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0001 Adding evictionStrategy docs

In response to this:

/cherrypick enterprise-4.17

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-cherrypick-robot]

@lahinson: new pull request created: #100347

In response to this:

/cherrypick enterprise-4.18

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-cherrypick-robot]

@lahinson: new pull request created: #100348

In response to this:

/cherrypick enterprise-4.19

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-cherrypick-robot]

@lahinson: new pull request created: #100349

In response to this:

/cherrypick enterprise-4.20

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.