Breaking changes20
Decentralized live migration limits now constrain target-pod creation
Affectsdecentralized live migrations subject to per-node or cluster migration limits(Inferred)
Before this fix, migration limits were not accurately applied to decentralized live migrations. Tests cover pending migrations when either limit is occupied and expect no target pod to be created.
Show release-note lines
- [PR #16011][kubevirt-bot] BugFix: The migration limit was not accurately being used with decentralized live migrations
github.com/kubevirt/kubevirt/releases/tag/v1.7.0VirtualMachinePool updates now default to proactive restarts
AffectsVirtualMachinePool resources(Inferred)
Previously, pools had no update-strategy API and only basic in-place update behavior. An explicitly configured opportunistic strategy updates the VM while the VMI changes naturally on restart; unmanaged makes no automatic VM updates, and proactive selection uses Random by default when no selection policy is configured.
Evidence“"description": "SelectionPolicy defines the priority in which VM instances are selected for proactive update Defaults to \"Random\" base policy when no SelectionPolicy is configured"” kubevirt/kubevirt/pull/15123 ↗ Show release-note lines
- [PR #15123][Sreeja1725] VMpool: Add UpdateStrategy support with Proactive, Opportunistic modes and Selection policies
github.com/kubevirt/kubevirt/releases/tag/v1.7.0VMI graceful shutdown sends one event per request
AffectsVMIs undergoing graceful shutdown
Previously, retries emitted repeated VMIGracefulShutdown events; with a large TerminationGracePeriodSeconds, these could exceed the event recorder's burst limit of 25 and cause later events, including the eventual shutdown event, to be dropped. Now only the initial request emits that event; retries remain logged in virt-handler.
Show release-note lines
- [PR #15759][lyarwood] Only a single `Signaled Graceful Shutdown` event is now sent to avoid spamming the event recorder during long graceful shutdown attempts
github.com/kubevirt/kubevirt/releases/tag/v1.7.0VMpool cleanup finalizer added
Affectssetups using VirtualMachinePools
When a pod is deleted manually or the VMpool replica count is scaled down while the pool is configured to preserve VM and PVC state, the VM could be deleted before reconciliation runs, putting PVC preservation at risk. The finalizer lets the controller perform cleanup first and helps preserve the PVC before VM deletion.
Evidence“Example usecase - When a pod is deleted manually or vmpool replica count is scaled down, and the vmpool is configured to preserve the state of the VM and PVC, it might be possible that the vm might have deleted by the time vmpool reconcile is triggered. Adding a finalizer will help in preserving the pvc before deleting the VM.” kubevirt/kubevirt/pull/15406 ↗ Show release-note lines
- [PR #15406][Sreeja1725] Add VMpool finalizer to ensure proper cleanup
github.com/kubevirt/kubevirt/releases/tag/v1.7.0VM container memory metrics renamed as request margins
AffectsPrometheus queries or rules using either VM container memory metric(Inferred)
Their descriptions now define the values as requested memory minus RSS or working set, which can be negative when usage exceeds the request; previously, they described current available memory.
Show release-note lines
- [PR #15504][sradco] Update metric kubevirt_vm_container_free_memory_bytes_based_on_rss and kubevirt_vm_container_free_memory_bytes_based_on_working_set_bytes names to kubevirt_vm_container_memory_request_margin_based_on_rss_bytes and kubevirt_vm_container_memory_request_margin_based_on_working_set_bytes so they will be clearer
github.com/kubevirt/kubevirt/releases/tag/v1.7.0ppc64le architecture configuration support removed
Affectsinstallations configured for the ppc64le architecture
Although the project already did not support or maintain ppc64le, its configuration and handling code existed before. This release removes that handling while leaving the schema field marked as deprecated.
Evidence“This PR **removes the `ppc64le` architecture configuration completely** and also removes associated code references and handling logic related to the `ppc64le` architecture.” kubevirt/kubevirt/pull/14976 ↗ Show release-note lines
- [PR #14976][dasionov] remove ppc64le architecture configuration support
github.com/kubevirt/kubevirt/releases/tag/v1.7.0Export server excludes lost+found
Affectsdata volumes with lost+found in their mounted contents, exported by the export server(Inferred)
When the export server lacked permission to handle files not created by KubeVirt or CDI, it could encounter permission issues with lost+found. Exports now omit that directory, and the export server excludes it from directory-permission checks.
Evidence“In some environments the export server might lack permissions to handle files that aren't created by Kubevirt or CDI, such as the lost+found directory.” kubevirt/kubevirt/pull/15509 ↗ Show release-note lines
- [PR #15509][alromeros] Bugfix: Exclude lost+found from export server
github.com/kubevirt/kubevirt/releases/tag/v1.7.0virtctl SSH and SCP now use host clients
Affectsvirtctl SSH or SCP usage, including invocations with --local-ssh(Inferred)
Before this release, virtctl included native SSH and SCP clients and the deprecated --local-ssh flag.
Show release-note lines
- [PR #15478][0xFelix] virtctl: The --local-ssh flag and native ssh and scp clients are removed from virtctl. From now on the local ssh and scp clients on a host are always wrapped by virtctl ssh and scp.
github.com/kubevirt/kubevirt/releases/tag/v1.7.0Migration memory-transfer metric renamed
Affectsmonitoring and automation consuming the migration memory-transfer metric(Inferred)
It was previously exposed as kubevirt_vmi_migration_disk_transfer_rate_bytes despite reporting memory transfer; it is now exposed as kubevirt_vmi_migration_memory_transfer_rate_bytes.
Evidence“Before this PR: The metric name is wrong and should be renamed to `kubevirt_vmi_migration_memory_transfer_rate_bytes`” kubevirt/kubevirt/pull/13500 ↗ Show release-note lines
- [PR #13500][brandboat] Fix incorrect metric name kubevirt_vmi_migration_disk_transfer_rate_bytes to kubevirt_vmi_migration_memory_transfer_rate_bytes
github.com/kubevirt/kubevirt/releases/tag/v1.7.0Descheduler eviction-in-progress annotation follows VMI eviction status
Affectssetups using the descheduler's eviction-in-progress annotation for VMI evictions
When a migration attempt failed, the annotation could be removed even though eviction would be retried, falsely signaling completion. It now reflects whether the VMI is marked for eviction and, during an active migration, is added only to the source pod; a stuck, uncanceled migration can stall a descheduler with a concurrent-eviction limit until an eviction completes or is canceled.
Evidence“Note: If migrations are stuck and evictions are never canceled (KubeVirt currently has no such mechanism), and the descheduler is configured with a limit on concurrent evictions, the descheduler may stall until some evictions complete or are manually canceled.” kubevirt/kubevirt/pull/15423 ↗ Show release-note lines
- [PR #15423][tiraboschi] Derive eviction-in-progress annotation from VMI eviction status
github.com/kubevirt/kubevirt/releases/tag/v1.7.0Legacy virtctl dot-based target parsing removed
Affectsvirtctl portforward, ssh, or scp targets using type/name.namespace syntax
Previously, the part after the last dot was treated as the namespace; now a dotted target is parsed as a resource name with no namespace unless a namespace is supplied using supported syntax. Using the old syntax could prompt host-key verification again and might require a manual known_hosts update.
Show release-note lines
- [PR #15475][0xFelix] virtctl (portfoward|ssh|scp): Drop support for legacy dot syntax. In case the old dot syntax was used virtctl could ask for verification of the host key again. In some cases the known_hosts file might need to be updated manually.
github.com/kubevirt/kubevirt/releases/tag/v1.7.0VMI foreground-delete finalizer now uses a domain-qualified name
AffectsVirtualMachineInstances using the KubeVirt foreground-delete finalizer(Inferred)
Removed ina future release
The old non-domain-qualified finalizer could trigger a Kubernetes warning that finalizer names should be domain-qualified. The controller now uses kubevirt.io/foregroundDeleteVirtualMachine and removes either the old or new finalizer when the VMI is finished or deleted; automation matching the old name may stop matching without an error.
Show release-note lines
- [PR #15096][lyarwood] The `foregroundDeleteVirtualMachine` has been deprecated and replaced with the domain-qualified `kubevirt.io/foregroundDeleteVirtualMachine`.
github.com/kubevirt/kubevirt/releases/tag/v1.7.0virt-operator scheduling restricted to control-plane nodes
AffectsKubeVirt installations with non-control-plane nodes available for virt-operator scheduling(Inferred)
Previously, virt-operator could be scheduled on non-control-plane nodes. Avoiding multiple replicas on one node remains a preference, so replicas may still share a control-plane node when there are more replicas than control-plane nodes.
Evidence“Avoiding multiple replicas on the same node is still only a preference, so multiple replicas will end up on the same node if there are more replicas than control-plane nodes.” kubevirt/kubevirt/pull/15157 ↗ Show release-note lines
- [PR #15157][jean-edouard] virt-operator won't schedule on worker nodes
github.com/kubevirt/kubevirt/releases/tag/v1.7.0KubeVirt synchronization status switches to synchronizationAddresses
Affectsclusters with DecentralizedLiveMigration enabled, especially those with a migration network or integrations reading KubeVirt CR synchronization-address status
With decentralized live migration enabled and a migration network configured, the operator previously could not advertise the migration-network IP and instead reported a pod-network IP in the singular status field. The status now includes addresses with the configured port; when several are available, the first is also reported in synchronizationAddress.
Evidence“The synchronization addresses one can use to connect to the synchronization controller, includes the port, if multiple addresses are available, the first one is reported in the synchronizationAddress field.” kubevirt/kubevirt/pull/15022 ↗ Show release-note lines
- [PR #15022][awels] The synchronization controller migration network IP address is advertised by the KubeVirt CR
github.com/kubevirt/kubevirt/releases/tag/v1.7.0Corrected virtctl expose Service selector
AffectsVMIs exposed with virtctl expose
Action requiredvirtctl expose from virtctl v1.7 and above does not work with older KubeVirt versions.
Previously, selecting by the full VMI name could miss the launcher pod when a hostname was set, and the launcher label could be truncated for long VMI names. Services now select by vmi.kubevirt.io/id.
Show release-note lines
- [PR #15783][orelmisan] Specify correct label selection when creating a service via virtctl expose. The expose command on virtctl v1.7 and above will not work with older KubeVirt versions.
github.com/kubevirt/kubevirt/releases/tag/v1.7.0Support for deprecated instancetype.kubevirt.io/v1alpha{1,2} APIs removed
Affectsinstancetype or preference resources, manifests, or clients using instancetype.kubevirt.io/v1alpha{1,2}(Inferred)
These API versions and their CRDs had remained supported despite being deprecated since v1.0.0.
Show release-note lines
- [PR #15400][lyarwood] The deprecated `instancetype.kubevirt.io/v1alpha{1,2}` API and CRDs have been removedgithub.com/kubevirt/kubevirt/releases/tag/v1.7.0Minimum for memoryOvercommit raised to 10
Affectsdeployments that set memoryOvercommit below 10
Action requiredmemoryOvercommit raised to 10 or higher before upgrading
Evidence“Important: deployments that set a memoryOvercommit value below 10 need to bump to 10+ before upgrading.” kubevirt/kubevirt/pull/15681 ↗ Show release-note lines
- [PR #15681][jean-edouard] Memory overcommit is now recalculated on migration.
github.com/kubevirt/kubevirt/releases/tag/v1.7.0VM unpause requests rejected during snapshots
AffectsVMs with vm.Status.SnapshotInProgress set
Previously, a VM could be unpaused while its snapshot was in progress; now the unpause request returns HTTP 409 Conflict.
Evidence“Make sure unpause will be rejected if `vm.Status.SnapshotInProgress` is not nil.” kubevirt/kubevirt/pull/15001 ↗ Show release-note lines
- [PR #15001][noamasu] bugfix: Enable vmsnapshot for paused VMs
github.com/kubevirt/kubevirt/releases/tag/v1.7.0Eviction protection for virt-launcher-owned hotplug pods during live migration
AffectsVMIs with virt-launcher-owned hotplug pods that can live migrate
Previously, a hotplug pod could be terminated during an ongoing live migration, potentially causing inconsistencies or failures before migration completed. The eviction webhook now protects the pod from premature eviction during migration.
Evidence“This PR extends the same protection to hotplug pods owned by the virt-launcher, ensuring they are not prematurely terminated during an ongoing live migration. This prevents potential inconsistencies or failures caused by the hotplug pod shutting down before the migration completes.” kubevirt/kubevirt/pull/15093 ↗ Show release-note lines
- [PR #15093][Acedus] bugfix: volume hotplug pod is no longer evicted when associated VM can live migrate.
github.com/kubevirt/kubevirt/releases/tag/v1.7.0virt-operator removes *_SHASUM image selection
Affectsvirt-operator setups that use *_SHASUM environment variables for image selection
Action requiredImage selection previously specified with *_SHASUM configured through the remaining *_IMAGE variables, using a tag, digest, or both.
Previously, *_SHASUM variables selected image checksums; they no longer select image versions. The remaining *_IMAGE variables select images by tag, digest, or both.
Show release-note lines
- [PR #15061][lyarwood] Support for all `*_SHASUM` environment variables has been removed from the `virt-operator` component. Users should instead use the remaining `*_IMAGE` environment variables to request a specific image version using a tag, digest or both.
github.com/kubevirt/kubevirt/releases/tag/v1.7.0