Backport: Changelog v1.1.0

[deckhouse-BOaTswain]

Changelog v1.1.0

Features

• [module] Added the D8VirtualizationDVCRInsufficientCapacityRisk alert, which warns of the risk of insufficient free space in the virtual machine image storage (DVCR). #1461

• [module] Added the KubeNodeAwaitingVirtualMachinesEvictionBeforeShutdown alert, which is triggered when the node hosting the virtual machines is about to shut down but VM evacuation is not yet complete. #1268

• [vm] Added the ability to migrate VMs using disks on local storage. Restrictions:

  • The feature is not available in the CE edition.
  • Migration is only possible for running VMs (phase: Running).
  • Migration of VMs with local disks connected via VirtualMachineBlockDeviceAttachment (hotplug) is not supported yet.

  Added the ability to migrate storage for VM disks (change StorageClass). Restrictions:

  • The feature is not available in the CE edition.
  • Migration is only possible for running VMs (phase: Running).
  • Storage migration for disks connected via VirtualMachineBlockDeviceAttachment (hotplug) is not supported yet. #1360

• [vmop] Added an operation with the Clone type to create a clone of a VM from an existing VM (VirtualMachineOperation .spec.type: Clone). #1418

Fixes

• [observability] Fixed the graph on the virtual machine dashboard that displays memory copy statistics during VM migration. #1474
• [vd] respect user-specified storage class when restoring from snapshot #1417
• [vmclass] Use qemu64 CPU model for Discovery and Features types to fix nested virtualization on AMD hosts #1446
• [vmop] Fix the problem where a disk that in the "Terminating" phase was wrongly added to kvvm's volumes during a restore operation in Strict mode. #1493
• [vmop] Fixed garbage collector behavior: previously, all VMOP objects were deleted after restarting the virtualization controller, ignoring cleanup rules. #1471

For more information, see the changelog and minor version release changes.

[sourcery-ai]

Reviewer's Guide

This PR backports the v1.1.0 changelog by adding two new files: a structured YAML changelog with component-level entries and a human-readable Markdown release note summarizing the new features and fixes.

File-Level Changes

Change	Details	Files
Add structured YAML changelog entries for v1.1.0	CI: alias linter, fix E2E teardown logs, correct delve debug variable Core: introduce end-to-end testing framework Docs: remove Cyrillic characters in documentation Module: add two new alerts (DVCR capacity risk, node VM eviction warning) Observability: correct VM migration memory copy graph VD: honor user storage class on snapshot restore VM: enable VM and storageClass migration for running VMs VMClass: switch to qemu64 CPU model for AMD nested virtualization VMOP: add Clone operation type; fix disk restore and garbage collector behavior	CHANGELOG/CHANGELOG-v1.1.0.yml
Add human-readable Markdown release notes for v1.1	Features: module alerts, VM/local-disk migration, storageClass migration, VM clone op Fixes: migration memory graph, snapshot restore storage class, AMD CPU model, VMOP restore/GC issues	CHANGELOG/CHANGELOG-v1.1.md

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey there - I've reviewed your changes and they look great!

Prompt for AI Agents

Please address the comments from this code review:

## Individual Comments

### Comment 1
<location> `CHANGELOG/CHANGELOG-v1.1.md:25` </location>
<code_context>
+ - **[observability]** Fixed the graph on the virtual machine dashboard that displays memory copy statistics during VM migration. [#1474](https://github.com/deckhouse/virtualization/pull/1474)
+ - **[vd]** respect user-specified storage class when restoring from snapshot [#1417](https://github.com/deckhouse/virtualization/pull/1417)
+ - **[vmclass]** Use qemu64 CPU model for Discovery and Features types to fix nested virtualization on AMD hosts [#1446](https://github.com/deckhouse/virtualization/pull/1446)
+ - **[vmop]** Fix the problem where a disk that in the "Terminating" phase  was wrongly added to kvvm's volumes during a restore operation in Strict mode. [#1493](https://github.com/deckhouse/virtualization/pull/1493)
+ - **[vmop]** Fixed garbage collector behavior: previously, all VMOP objects were deleted after restarting the virtualization controller, ignoring cleanup rules. [#1471](https://github.com/deckhouse/virtualization/pull/1471)
+
</code_context>

<issue_to_address>
**issue (typo):** Add 'is' to 'a disk that is in the "Terminating" phase' for grammatical correctness.

Update the phrase to 'a disk that is in the "Terminating" phase' for correct grammar.

```suggestion
 - **[vmop]** Fix the problem where a disk that is in the "Terminating" phase was wrongly added to kvvm's volumes during a restore operation in Strict mode. [#1493](https://github.com/deckhouse/virtualization/pull/1493)
```
</issue_to_address>

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[sourcery-ai]

issue (typo): Add 'is' to 'a disk that is in the "Terminating" phase' for grammatical correctness.

Update the phrase to 'a disk that is in the "Terminating" phase' for correct grammar.

Suggested change

	- **[vmop]** Fix the problem where a disk that in the "Terminating" phase was wrongly added to kvvm's volumes during a restore operation in Strict mode. [#1493](https://github.com/deckhouse/virtualization/pull/1493)
	- **[vmop]** Fix the problem where a disk that is in the "Terminating" phase was wrongly added to kvvm's volumes during a restore operation in Strict mode. [#1493](https://github.com/deckhouse/virtualization/pull/1493)