docs: add crd examples

Signed-off-by: Vladislav Panfilov <vladislav.panfilov@flant.com>

Author: prismagod

crds/clustervirtualimages.yaml

@@ -58,6 +58,16 @@ spec:
             With this resource in the cluster, a container image is created and stored in a dedicated Deckhouse Virtualization Container Registry (DVCR).
 
             **Note:** The `metadata.name` field must comply with [Kubernetes object naming conventions](https://kubernetes.io/docs/concepts/overview/working-with-objects/names/) and must not exceed 48 characters.
+          x-examples:
+            - apiVersion: virtualization.deckhouse.io/v1alpha2
+              kind: ClusterVirtualImage
+              metadata:
+                name: ubuntu-24-04
+              spec:
+                dataSource:
+                  type: HTTP
+                  http:
+                    url: https://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.img
           properties:
             apiVersion:
               description: |-

crds/nodeusbdevices.yaml

@@ -47,6 +47,13 @@ spec:
             Represents a USB device discovered on a specific node in the cluster.
             This resource is created automatically by the DRA (Dynamic Resource Allocation) system
             when a USB device is detected on a node.
+          x-examples:
+            - apiVersion: virtualization.deckhouse.io/v1alpha2
+              kind: NodeUSBDevice
+              metadata:
+                name: logitech-webcam
+              spec:
+                assignedNamespace: my-project
           properties:
             apiVersion:
               description: |-

crds/virtualdisks.yaml

@@ -60,6 +60,15 @@ spec:
             Once a VirtualDisk is created, the following fields in `.spec.persistentVolumeClaim` can be changed: `size` and `storageClassName`. All other fields are immutable.
 
             **Note:** The `metadata.name` field must comply with [Kubernetes object naming conventions](https://kubernetes.io/docs/concepts/overview/working-with-objects/names/) and must not exceed 60 characters.
+          x-examples:
+            - apiVersion: virtualization.deckhouse.io/v1alpha2
+              kind: VirtualDisk
+              metadata:
+                name: blank-disk
+              spec:
+                persistentVolumeClaim:
+                  storageClassName: rv-thin-r2
+                  size: 100Mi
           properties:
             apiVersion:
               description: |-

crds/virtualdisksnapshots.yaml

@@ -29,6 +29,14 @@ spec:
             Provides a resource for creating snapshots of existing virtual disks, which can be used as data sources for generating new virtual disks.
 
             When running, a VolumeSnapshot resource is created.
+          x-examples:
+            - apiVersion: virtualization.deckhouse.io/v1alpha2
+              kind: VirtualDiskSnapshot
+              metadata:
+                name: linux-vm-root-snapshot
+              spec:
+                requiredConsistency: true
+                virtualDiskName: linux-vm-root
           required:
             - spec
           properties:

crds/virtualimages.yaml

@@ -61,6 +61,17 @@ spec:
             With this resource in the cluster, a container image is created and stored in a dedicated Deckhouse Virtualization Container Registry (DVCR) or PVC, with the data filled in from the source.
 
             **Note:** The `metadata.name` field must comply with [Kubernetes object naming conventions](https://kubernetes.io/docs/concepts/overview/working-with-objects/names/) and must not exceed 49 characters.
+          x-examples:
+            - apiVersion: virtualization.deckhouse.io/v1alpha2
+              kind: VirtualImage
+              metadata:
+                name: ubuntu-24-04
+              spec:
+                storage: ContainerRegistry
+                dataSource:
+                  type: HTTP
+                  http:
+                    url: https://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.img
           properties:
             apiVersion:
               description: |-

crds/virtualmachineblockdeviceattachments.yaml

@@ -50,6 +50,16 @@ spec:
           description: |-
             VirtualMachineBlockDeviceAttachment provides a hot plug for attaching a disk to a virtual machine.
             Disks are always attached using the SCSI bus, regardless of the enableParavirtualization setting.
+          x-examples:
+            - apiVersion: virtualization.deckhouse.io/v1alpha2
+              kind: VirtualMachineBlockDeviceAttachment
+              metadata:
+                name: attach-blank-disk
+              spec:
+                blockDeviceRef:
+                  kind: VirtualDisk
+                  name: blank-disk
+                virtualMachineName: linux-vm
           properties:
             apiVersion:
               description: |-

crds/virtualmachineclasses.yaml

@@ -44,6 +44,14 @@ spec:
           description: |-
             VirtualMachineClass resource describes CPU requirements, node placement, and sizing policy for VM resources.
             A resource cannot be deleted as long as it is used in one of the VMs.
+          x-examples:
+            - apiVersion: virtualization.deckhouse.io/v1alpha2
+              kind: VirtualMachineClass
+              metadata:
+                name: host
+              spec:
+                cpu:
+                  type: Host
           properties:
             apiVersion:
               description: |-

crds/virtualmachineipaddresses.yaml

@@ -22,6 +22,14 @@ spec:
         openAPIV3Schema:
           description: |
             Defines the IP address for a virtual machine.
+          x-examples:
+            - apiVersion: virtualization.deckhouse.io/v1alpha2
+              kind: VirtualMachineIPAddress
+              metadata:
+                name: linux-vm-custom-ip
+              spec:
+                type: Static
+                staticIP: 10.66.20.77
           properties:
             apiVersion:
               type: string

crds/virtualmachineoperations.yaml

@@ -48,6 +48,14 @@ spec:
           description:
             VirtualMachineOperation enables declarative management of virtual
             machine state changes.
+          x-examples:
+            - apiVersion: virtualization.deckhouse.io/v1alpha2
+              kind: VirtualMachineOperation
+              metadata:
+                generateName: restart-linux-vm-
+              spec:
+                virtualMachineName: linux-vm
+                type: Restart
           properties:
             apiVersion:
               description: |-

crds/virtualmachinerestores.yaml

@@ -40,6 +40,13 @@ spec:
           description:
             VirtualMachineRestore provides a resource for restoring a virtual
             machine and all associated resources from a snapshot.
+          x-examples:
+            - apiVersion: virtualization.deckhouse.io/v1alpha2
+              kind: VirtualMachineRestore
+              metadata:
+                name: restore-linux-vm
+              spec:
+                virtualMachineSnapshotName: linux-vm-snapshot
           properties:
             apiVersion:
               description: |-