feat(vm): autogenerate crd

api/Taskfile.dist.yaml

@@ -15,7 +15,9 @@ tasks:
     deps:
       - _ensure:k8s-codegen-mod
       - _ensure:k8s-kube-openapi
-    cmd: ./scripts/update-codegen.sh all
+    cmds:
+      - ./scripts/update-codegen.sh all
+      - task: format:yaml
 
   generate:core:
     desc: "Regenerate code for core components."
@@ -40,7 +42,17 @@ tasks:
     desc: "Regenerate crds"
     deps:
       - _ensure:k8s-controller-gen
-    cmd: ./scripts/update-codegen.sh crds
+    cmds:
+      - ./scripts/update-codegen.sh crds
+      - task: format:yaml
+
+  format:yaml:
+    desc: "Format non-templated YAML files, e.g. CRDs"
+    cmds:
+      - |
+        cd ../ && docker run --rm \
+          -v ./:/tmp/virt ghcr.io/deckhouse/virtualization/prettier:3.2.5 \
+          sh -c "cd /tmp/virt ; prettier -w \"**/*.yaml\" \"**/*.yml\""
 
   _ci:verify-gen:
     desc: "Check generated files are up-to-date."

api/core/v1alpha2/block_device.go

@@ -18,19 +18,33 @@ package v1alpha2
 
 type BlockDeviceSpecRef struct {
 	Kind BlockDeviceKind `json:"kind"`
-	Name string          `json:"name"`
+	// The name of attached resource.
+	Name string `json:"name"`
 }
 
 type BlockDeviceStatusRef struct {
-	Kind                                    BlockDeviceKind `json:"kind"`
-	Name                                    string          `json:"name"`
-	Size                                    string          `json:"size"`
-	Target                                  string          `json:"target"`
-	Attached                                bool            `json:"attached"`
-	Hotplugged                              bool            `json:"hotplugged,omitempty"`
-	VirtualMachineBlockDeviceAttachmentName string          `json:"virtualMachineBlockDeviceAttachmentName,omitempty"`
+	Kind BlockDeviceKind `json:"kind"`
+	// The name of attached resource.
+	Name string `json:"name"`
+	// The size of attached block device.
+	Size string `json:"size"`
+	// The block device is attached to the virtual machine.
+	Attached bool `json:"attached"`
+	// The name of attached block device.
+	// +kubebuilder:example=sda
+	Target string `json:"target,omitempty"`
+	// Block device is attached via hot plug connection.
+	Hotplugged bool `json:"hotplugged,omitempty"`
+	// The name of the `VirtualMachineBlockDeviceAttachment` resource that defines hot plug disk connection to the virtual machine.
+	VirtualMachineBlockDeviceAttachmentName string `json:"virtualMachineBlockDeviceAttachmentName,omitempty"`
 }
 
+// The BlockDeviceKind is a type of the block device. Options are:
+//
+// * `ClusterVirtualImage` — Use `ClusterVirtualImage` as the disk. This type is always mounted in RO mode. If the image is an iso-image, it will be mounted as a CDROM device.
+// * `VirtualImage` — Use `VirtualImage` as the disk. This type is always mounted in RO mode. If the image is an iso-image, it will be mounted as a CDROM device.
+// * `VirtualDisk` — Use `VirtualDisk` as the disk. This type is always mounted in RW mode.
+// +kubebuilder:validation:Enum:={ClusterVirtualImage,VirtualImage,VirtualDisk}
 type BlockDeviceKind string
 
 const (

api/core/v1alpha2/virtual_machine_class.go

@@ -35,7 +35,7 @@ const (
 // +kubebuilder:object:root=true
 // +kubebuilder:metadata:labels={heritage=deckhouse,module=virtualization}
 // +kubebuilder:subresource:status
-// +kubebuilder:resource:categories=virtualization,scope=Cluster,shortName={vmc,vmcs,vmclass,vmclasses},singular=virtualmachineclass
+// +kubebuilder:resource:categories={virtualization},scope=Cluster,shortName={vmc,vmcs,vmclass,vmclasses},singular=virtualmachineclass
 // +kubebuilder:printcolumn:name="Phase",type="string",JSONPath=".status.phase",description="VirtualMachineClass phase."
 // +kubebuilder:printcolumn:name="Age",type="date",JSONPath=".metadata.creationTimestamp",description="Time of creation resource."
 // +genclient
@@ -55,7 +55,7 @@ type VirtualMachineClassList struct {
 	metav1.TypeMeta `json:",inline"`
 	metav1.ListMeta `json:"metadata"`
 
-	// Items provides a list of CDIs
+	// Items provides a list of VirtualMachineClasses
 	Items []VirtualMachineClass `json:"items"`
 }
 

api/core/v1alpha2/vmaffinity.go

@@ -21,6 +21,11 @@ import (
 	metav1 "k8s.io/apimachinery/pkg/apis/meta/v1"
 )
 
+// VMAffinity [The same](https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#affinity-and-anti-affinity) as in the pods `spec.affinity` parameter in Kubernetes;
+//
+// The affinity setting is completely similar to the above documentation, the only difference is in the names of some parameters. In fact, the following analogs are used:
+// * podAffinity -> virtualMachineAndPodAffinity
+// * podAffinityTerm -> virtualMachineAndPodAffinityTerm
 type VMAffinity struct {
 	NodeAffinity                     *corev1.NodeAffinity              `json:"nodeAffinity,omitempty"`
 	VirtualMachineAndPodAffinity     *VirtualMachineAndPodAffinity     `json:"virtualMachineAndPodAffinity,omitempty"`

api/core/v1alpha2/vmcondition/condition.go

@@ -45,6 +45,8 @@ func (r Reason) String() string {
 }
 
 const (
+	ReasonUnknown Reason = "Unknown"
+
 	ReasonAgentNotReady Reason = "AgentNotReady"
 
 	ReasonClassReady    Reason = "VirtualMachineClassReady"