net: Add live update NAD reference documentation#979
net: Add live update NAD reference documentation#979kubevirt-bot merged 2 commits intokubevirt:mainfrom
Conversation
|
/cc @orelmisan , @nirdothan |
There was a problem hiding this comment.
Thank you @frenzyfriday.
- Please don't let AI spit out so much redundant text. It exhausts the readers and adds a maintenance burden on the writers.
- Please follow the standard formatting that you see in other pages Look at @orelmisan's PRs).
- I might be missing it but how is the page linked to the guide?
| @@ -0,0 +1,215 @@ | |||
| # Live Update Network Attachment Definition Reference | |||
There was a problem hiding this comment.
I'm not sure about the release note. Don't think that we need to add everything we document in a release-note. Specifically you indicated the FG name and not the description of the feature.
There was a problem hiding this comment.
Ack, removed the release note
| Release: | ||
|
|
||
| - v1.8.0: Beta | ||
| - v1.9.0: GA |
There was a problem hiding this comment.
I have a PR to graduate the FG in main. I can push for it once the flake is fixed and probably it will merge by 1.9 codefreeze
| - The `LiveUpdateNADRef` [feature-gate](https://kubevirt.io/user-guide/operations/activating_feature_gates/#how-to-activate-a-feature-gate) must be enabled (for v1.8.x Beta release) | ||
| - The target NetworkAttachmentDefinition must exist in the same namespace | ||
|
|
||
| > **Note**: From KubeVirt v1.9, the feature gate is no longer needed as the feature reached GA. |
There was a problem hiding this comment.
Per my comment above. Need to figure out if we are already documenting v1.9.
|
|
||
| > **Note**: From KubeVirt v1.9, the feature gate is no longer needed as the feature reached GA. | ||
|
|
||
| ## What Gets Updated |
There was a problem hiding this comment.
Please consider dropping this whole paragraph. You've already explained that and it looks like AI is just enjoying spitting out text in bold.
| - **Tenant Migration**: Moving VMs between different tenant networks | ||
| - **Network Segmentation**: Changing network isolation boundaries for running workloads | ||
|
|
||
| ## Compatibility with Multus Dynamic Networks Controller |
There was a problem hiding this comment.
This is important. Please put it in a Note or warning, according to our standard format. (look for !!!)
There was a problem hiding this comment.
I havent tested it with DNC yet. Lemme add this section in a follow up
There was a problem hiding this comment.
Why don't you write that it's currently not supported, and then if it works remove it in a followup?
|
Last change addresses Nir's comments and introduces human edits |
3969a5c to
fb24f7f
Compare
|
Last few changes (after Nir's review) addresses Nir's comments, links the NAD update page to the main network page and changes the name of the page from |
| - masquerade: {} | ||
| name: defaultnetwork |
There was a problem hiding this comment.
nit: This is not really relevant to express this feature.
| If automatic migration is not configured, a migration must be manually triggered. | ||
| Please refer to the [Live Migration](../../compute/live_migration.md) documentation for more information. |
There was a problem hiding this comment.
This is not relevant, users are not allowed to migrate VMs, only admins can.
I would expect that if the rollout strategy is not LiveUpdate, then the VM should show it needs a restart. Isn't that the case?
There was a problem hiding this comment.
If the WorkloadUpdateStrategy and VMRolloutStrategy are not set the VM will still show
- last...
reason: AutoMigrationDueToLiveUpdate
status: "True"
type: MigrationRequired```
but it will not migrate.
There was a problem hiding this comment.
It sounds like a bug to me.
I guess we missed it in the VEP.
And I do not understand how WorkloadUpdateStrategy is relevant. It is supposed to affect upgrades AFAIU.
There was a problem hiding this comment.
+1 I find it hard to understand why we could have such a non-actionable condition MigrationRequired - @orelmisan could it be a leftover?
@jean-edouard fyi
There was a problem hiding this comment.
If the
WorkloadUpdateStrategyandVMRolloutStrategyare not set the VM will still show- last... reason: AutoMigrationDueToLiveUpdate status: "True" type: MigrationRequired```but it will not migrate.
kubevirt/kubevirt#17328 tracks this issue and contains the relevant details.
There was a problem hiding this comment.
I have also opened kubevirt/kubevirt#17329 to treat the odd dependency on the cluster upgrade knob.
There was a problem hiding this comment.
Sorry, removed the line about migration here
| If automatic migration is not configured, a migration must be manually triggered. | ||
| Please refer to the [Live Migration](../../compute/live_migration.md) documentation for more information. | ||
|
|
||
| ## Limitations |
There was a problem hiding this comment.
Please add the scale issue: When a bulk of VMs are updated, the change occurs per the live migration parallel limitations (link may be useful).
| ## Limitations | ||
| - Moving to a different CNI type may fail, specially if the new CNI type requires additional configurations to be done. | ||
| - Switching to a new binding type/binding plugin is not supported | ||
| - Only migratable VMs can be updated |
There was a problem hiding this comment.
What will happen to the ones who are not migratable?
Document the live update NAD reference feature which allows changing the NetworkAttachmentDefinition reference on running VMs through live migration without requiring a reboot. Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com> Signed-off-by: Ananya Banerjee <anbanerj@redhat.com>
This commit adds a link to nad_reference.md under network/hotplug. Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com> Signed-off-by: Ananya Banerjee <anbanerj@redhat.com>
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: EdDev The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
orelmisan
left a comment
There was a problem hiding this comment.
Thank you @frenzyfriday!
Giving @nirdothan a chance to feedback
/hold
Document the live update NAD reference feature which allows changing the NetworkAttachmentDefinition reference on running VMs through live migration without requiring a reboot.
VEP tracking issue: kubevirt/enhancements#140
What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)format, will close the issue(s) when PR gets merged):Fixes #
Special notes for your reviewer:
Checklist
This checklist is not enforcing, but it's a reminder of items that could be relevant to every PR.
Approvers are expected to review this list.
Release note: