fix docs for VM live migration network#72586
fix docs for VM live migration network#72586johnsimcall wants to merge 1 commit intoopenshift:mainfrom
Conversation
Avoid using the openshift#2 callout/identifier multiple times. Instruct users to create the net-attach-def in a particular namespace. Avoid using NAD abbreviation when the short form of NetworkAttachmentDefinition is net-attach-def
|
Hi @johnsimcall. 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 Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions 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. |
|
@openshift/team-documentation - would you please review this minor change that improves the documentation for creating a dedicated live migration network for KubeVirt / OpenShift Virtualization? |
|
/ok-to-test |
|
🤖 Fri Mar 08 19:05:31 - Prow CI generated the docs preview: |
|
@sjhala-ccs, can you please review this networking-related change? Thanks. :) |
sjhala-ccs
left a comment
There was a problem hiding this comment.
@johnsimcall Thank you for catching this doc issue. The call out numbering and description seems fine for 4.13 and earlier versions. The changes were likely introduced during the network docs reorganization applied to 4.14+.
| <4> Specify an IP address range for the secondary network. This range must not overlap the IP addresses of the main network. | ||
| <2> The `NetworkAttachmentDefinition` object must be created in the {CNVNamespace} namespace. | ||
| <3> Specify the name of the NIC to be used for live migrations. | ||
| <4> Specify the name of the CNI plugin that provides the network for the `NetworkAttachmentDefinition`. |
There was a problem hiding this comment.
| <4> Specify the name of the CNI plugin that provides the network for the `NetworkAttachmentDefinition`. | |
| <4> Specify the name of the CNI plugin that provides the network for the network attachment definition. |
| <2> Specify the name of the NIC to be used for live migration. | ||
| <3> Specify the name of the CNI plugin that provides the network for the NAD. | ||
| <4> Specify an IP address range for the secondary network. This range must not overlap the IP addresses of the main network. | ||
| <2> The `NetworkAttachmentDefinition` object must be created in the {CNVNamespace} namespace. |
There was a problem hiding this comment.
| <2> The `NetworkAttachmentDefinition` object must be created in the {CNVNamespace} namespace. | |
| <2> Specify the namespace where the `NetworkAttachmentDefinition` object resides. This must be `{CNVNamespace}`. |
|
@johnsimcall: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions 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. |
|
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
|
The This is because your PR targets the If the update in your PR does NOT apply to version 4.18 onward, please re-target this PR to go directly into the appropriate version branch or branches (enterprise-4.x) instead of main. |
|
Stale issues rot after 30d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle rotten |
|
Rotten issues close after 30d of inactivity. Reopen the issue by commenting /close |
|
@openshift-bot: Closed this PR. DetailsIn response to this:
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. |
Avoid using the number-2 callout/identifier multiple times. Instruct users to create the net-attach-def in a particular namespace. Avoid using NAD abbreviation when the short form of NetworkAttachmentDefinition is net-attach-def
Version(s):
Applies to all versions of OpenShift documentation
Issue:
No issue exists. Do I need to create a Jira / Bugzilla for a minor change like this?
Link to docs preview:
QE review:
Additional information: