Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -67,6 +67,14 @@ This is the first phase of phasing out the aggregated API server: in a future re

For more information, see [Enable native v3 CRDs](../operations/native-v3-crds.mdx) and [Migrate from API server to native CRDs](../operations/crd-migration.mdx).

### Live migration for KubeVirt VMs

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch — confirmed. kubevirt-networking.mdx marks live migration support as a tech preview feature (persistent IPs are GA). Fixed in 029d10a: added the (tech preview) heading suffix to match the other tech-preview items in this section, and added a line noting live migration is tech preview and currently requires BGP networking without overlay.


$[prodname] now provides first-class networking for KubeVirt virtual machines, including persistent IP addresses and BGP-aware live migration.
A VM keeps the same IP address across reboots, pod evictions, and live migrations, and $[prodname] uses route priority to steer traffic to the new host as a running VM migrates between nodes without breaking established connections.
In single-rack iBGP deployments this works automatically; in multi-rack or eBGP topologies, you configure `BGPFilter` resources to propagate route priority across AS boundaries.

For more information, see [Calico Enterprise networking for KubeVirt](../networking/kubevirt/kubevirt-networking.mdx) and [BGP routing for KubeVirt live migration](../networking/kubevirt/live-migration-bgp.mdx).

{/* End 3.23.0-2.0 features */}

{/* Start 3.23.0-1.0 features */}
Expand Down