kube_schema 1.8.0 → 1.9.0

data/schemas/kubevirt-definitions.json

@@ -324,6 +324,19 @@
       }
     }
   },
+  "v1.ClaimRequest": {
+    "type": "object",
+    "properties": {
+      "claimName": {
+        "description": "ClaimName references the name of an entry in the VMI's spec.resourceClaims[] array. The referenced entry may use either resourceClaimName or resourceClaimTemplateName.",
+        "type": "string"
+      },
+      "requestName": {
+        "description": "RequestName specifies which request from the ResourceClaim/ResourceClaimTemplate spec.devices.requests array this claim request corresponds to.",
+        "type": "string"
+      }
+    }
+  },
   "v1.ClientPassthroughDevices": {
     "description": "Represent a subset of client devices that can be accessed by VMI. At the moment only, USB devices using Usbredir's library and tooling. Another fit would be a smartcard with libcacard.\n\nThe struct is currently empty as there is no immediate request for user-facing APIs. This structure simply turns on USB redirection of UsbClientPassthroughMaxNumberOf devices.",
     "type": "object"
@@ -2285,6 +2298,10 @@
       "permittedHostDevices": {
         "$ref": "#/definitions/v1.PermittedHostDevices"
       },
+      "persistentReservationConfiguration": {
+        "description": "PersistentReservationConfiguration controls the deployment of additional resources required for using SCSI persistent reservation in VMs",
+        "$ref": "#/definitions/v1.PersistentReservationConfiguration"
+      },
       "roleAggregationStrategy": {
         "description": "RoleAggregationStrategy controls whether RBAC cluster roles should be aggregated to the default Kubernetes roles (admin, edit, view). When set to \"AggregateToDefault\" (default) or not specified, the aggregate-to-* labels are added to the cluster roles. When set to \"Manual\", the labels are not added, and roles will not be aggregated to the default roles. Setting this field to \"Manual\" requires the OptOutRoleAggregation feature gate to be enabled. This is an Alpha feature and subject to change.",
         "type": "string"
@@ -2950,6 +2967,10 @@
       },
       "pod": {
         "$ref": "#/definitions/v1.PodNetwork"
+      },
+      "resourceClaim": {
+        "description": "ResourceClaim represents a network resource requested via a VMI spec.resourceClaims[] entry, backed by either a Kubernetes ResourceClaim or ResourceClaimTemplate. This field should only be configured if the NetworkDevicesWithDRA feature-gate is enabled. This feature is in alpha.",
+        "$ref": "#/definitions/v1.ClaimRequest"
       }
     }
   },
@@ -3191,6 +3212,15 @@
       }
     }
   },
+  "v1.PersistentReservationConfiguration": {
+    "type": "object",
+    "properties": {
+      "enabled": {
+        "description": "Enabled controls the deployment of additional resources like the pr-helper container for enabling the use of the SCSI persistent reservation VMs, defaults to False.",
+        "type": "boolean"
+      }
+    }
+  },
   "v1.PersistentVolumeClaimInfo": {
     "description": "PersistentVolumeClaimInfo contains the relavant information virt-handler needs cached about a PVC",
     "type": "object",
@@ -5776,6 +5806,27 @@
       }
     }
   },
+  "v1.VirtualMachineInstanceResourceClaim": {
+    "type": "object",
+    "required": [
+      "name"
+    ],
+    "properties": {
+      "name": {
+        "description": "Name uniquely identifies this resource claim inside the VMI. This field is required and must be a DNS_LABEL.",
+        "type": "string",
+        "default": ""
+      },
+      "resourceClaimName": {
+        "description": "ResourceClaimName is the name of a ResourceClaim object in the same namespace as this VMI.\n\nExactly one of ResourceClaimName and ResourceClaimTemplateName must be set.",
+        "type": "string"
+      },
+      "resourceClaimTemplateName": {
+        "description": "ResourceClaimTemplateName is the name of a ResourceClaimTemplate object in the same namespace as this VMI.\n\nThe template name is passed through to the generated virt-launcher Pod spec. From the Pod spec, the template is used to create a new ResourceClaim, which is bound to the virt-launcher Pod. When the virt-launcher Pod is deleted, the ResourceClaim is also deleted. The generated ResourceClaim name is unique and is recorded in pod.status.resourceClaimStatuses.\n\nExactly one of ResourceClaimName and ResourceClaimTemplateName must be set.",
+        "type": "string"
+      }
+    }
+  },
   "v1.VirtualMachineInstanceSpec": {
     "description": "VirtualMachineInstanceSpec is a description of a VirtualMachineInstance.",
     "type": "object",
@@ -5856,11 +5907,11 @@
         "$ref": "#/definitions/v1.Probe"
       },
       "resourceClaims": {
-        "description": "ResourceClaims define which ResourceClaims must be allocated and reserved before the VMI, hence virt-launcher pod is allowed to start. The resources will be made available to the domain which consumes them by name.\n\nThis is an alpha field and requires enabling the DynamicResourceAllocation feature gate in kubernetes\n https://kubernetes.io/docs/concepts/scheduling-eviction/dynamic-resource-allocation/\nThis field should only be configured if one of the feature-gates GPUsWithDRA or HostDevicesWithDRA is enabled. This feature is in alpha.",
+        "description": "ResourceClaims define which ResourceClaims must be allocated and reserved before the VMI, hence virt-launcher pod is allowed to start. The resources will be made available to the domain which consumes them by name.\n\nThis is an alpha field and requires enabling the DynamicResourceAllocation feature gate in kubernetes\n https://kubernetes.io/docs/concepts/scheduling-eviction/dynamic-resource-allocation/\nThis field should only be configured if one of the feature-gates GPUsWithDRA, HostDevicesWithDRA, or NetworkDevicesWithDRA is enabled. This feature is in alpha.",
         "type": "array",
         "items": {
           "default": {},
-          "$ref": "#/definitions/io.k8s.api.core.v1.PodResourceClaim"
+          "$ref": "#/definitions/v1.VirtualMachineInstanceResourceClaim"
         },
         "x-kubernetes-list-map-keys": [
           "name"

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: kube_schema
 version: !ruby/object:Gem::Version
-  version: 1.8.0
+  version: 1.9.0
 platform: ruby
 authors:
 - Nathan K