docs: update due v1.2.0

[fl64]

Description

update due v1.2.0

Why do we need it, and what problem does it solve?

What is the expected result?

Checklist

• The code is covered by unit tests.
• e2e tests passed.
• Documentation updated according to the changes.
• Changes were tested in the Kubernetes cluster manually.

Changelog entries

section: module
type: chore
summary: update due v1.2.0
impact_level: low

[sourcery-ai]

Reviewer's Guide

Introduces warning alerts clarifying project-level resource scope and refines disk and live migration guidance in the user guide for version 1.2.0.

Flow diagram for VM image resource selection and scope

flowchart TD
    A["User wants to use VM image"] --> B["Choose resource type"]
    B --> C["VirtualImage (project/namespace scope)"]
    B --> D["ClusterVirtualImage (cluster-wide scope)"]
    C --> E["Image available only in project/namespace"]
    D --> F["Image available cluster-wide"]

Loading

File-Level Changes

Change	Details	Files
Clarify VirtualImage resource scope with warning alerts	Added warning block explaining VirtualImage is project-scoped Referenced ClusterVirtualImage for cluster-level image usage	docs/USER_GUIDE.ru.md docs/USER_GUIDE.md
Refine disk section wording and formatting	Reworded disk purpose and storage type descriptions Standardized terminology for VolumeBindingMode and AccessMode	docs/USER_GUIDE.ru.md
Add live migration prerequisites and policy guidance	Inserted warning about disk availability on target nodes for live migration Noted need for liveMigrationPolicy configuration in VM spec	docs/USER_GUIDE.ru.md docs/USER_GUIDE.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.

[neermilov]

Maybe it would be helpful to add a note to documentation that in order to use the d8 data export download feature, you'll need to enable the "storage-volume-data-manager" module due to an error:

Error: DataExporter create error: no matches for kind 'DataExport' in version 'storage.deckhouse.io/v1alpha1'