kubevirt 0.2.0 → 0.3.0

data/docs/K8sIoApiCoreV1PersistentVolumeClaimSpec.md

@@ -10,7 +10,7 @@
 | **resources** | [**K8sIoApiCoreV1VolumeResourceRequirements**](K8sIoApiCoreV1VolumeResourceRequirements.md) |  | [optional] |
 | **selector** | [**K8sIoApimachineryPkgApisMetaV1LabelSelector**](K8sIoApimachineryPkgApisMetaV1LabelSelector.md) |  | [optional] |
 | **storage_class_name** | **String** | storageClassName is the name of the StorageClass required by the claim. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#class-1 | [optional] |
-| **volume_attributes_class_name** | **String** | volumeAttributesClassName may be used to set the VolumeAttributesClass used by this claim. If specified, the CSI driver will create or update the volume with the attributes defined in the corresponding VolumeAttributesClass. This has a different purpose than storageClassName, it can be changed after the claim is created. An empty string value means that no VolumeAttributesClass will be applied to the claim but it's not allowed to reset this field to empty string once it is set. If unspecified and the PersistentVolumeClaim is unbound, the default VolumeAttributesClass will be set by the persistentvolume controller if it exists. If the resource referred to by volumeAttributesClass does not exist, this PersistentVolumeClaim will be set to a Pending state, as reflected by the modifyVolumeStatus field, until such as a resource exists. More info: https://kubernetes.io/docs/concepts/storage/volume-attributes-classes/ (Beta) Using this field requires the VolumeAttributesClass feature gate to be enabled (off by default). | [optional] |
+| **volume_attributes_class_name** | **String** | volumeAttributesClassName may be used to set the VolumeAttributesClass used by this claim. If specified, the CSI driver will create or update the volume with the attributes defined in the corresponding VolumeAttributesClass. This has a different purpose than storageClassName, it can be changed after the claim is created. An empty string or nil value indicates that no VolumeAttributesClass will be applied to the claim. If the claim enters an Infeasible error state, this field can be reset to its previous value (including nil) to cancel the modification. If the resource referred to by volumeAttributesClass does not exist, this PersistentVolumeClaim will be set to a Pending state, as reflected by the modifyVolumeStatus field, until such as a resource exists. More info: https://kubernetes.io/docs/concepts/storage/volume-attributes-classes/ | [optional] |
 | **volume_mode** | **String** | volumeMode defines what type of volume is required by the claim. Value of Filesystem is implied when not included in claim spec.  Possible enum values:  - `\"Block\"` means the volume will not be formatted with a filesystem and will remain a raw block device.  - `\"Filesystem\"` means the volume will be or is formatted with a filesystem.  - `\"FromStorageProfile\"` means the volume mode will be auto selected by CDI according to a matching StorageProfile | [optional] |
 | **volume_name** | **String** | volumeName is the binding reference to the PersistentVolume backing this claim. | [optional] |
 

data/docs/K8sIoApiCoreV1PodAntiAffinity.md

@@ -4,7 +4,7 @@
 
 | Name | Type | Description | Notes |
 | ---- | ---- | ----------- | ----- |
-| **preferred_during_scheduling_ignored_during_execution** | [**Array<K8sIoApiCoreV1WeightedPodAffinityTerm>**](K8sIoApiCoreV1WeightedPodAffinityTerm.md) | The scheduler will prefer to schedule pods to nodes that satisfy the anti-affinity expressions specified by this field, but it may choose a node that violates one or more of the expressions. The node that is most preferred is the one with the greatest sum of weights, i.e. for each node that meets all of the scheduling requirements (resource request, requiredDuringScheduling anti-affinity expressions, etc.), compute a sum by iterating through the elements of this field and adding \"weight\" to the sum if the node has pods which matches the corresponding podAffinityTerm; the node(s) with the highest sum are the most preferred. | [optional] |
+| **preferred_during_scheduling_ignored_during_execution** | [**Array<K8sIoApiCoreV1WeightedPodAffinityTerm>**](K8sIoApiCoreV1WeightedPodAffinityTerm.md) | The scheduler will prefer to schedule pods to nodes that satisfy the anti-affinity expressions specified by this field, but it may choose a node that violates one or more of the expressions. The node that is most preferred is the one with the greatest sum of weights, i.e. for each node that meets all of the scheduling requirements (resource request, requiredDuringScheduling anti-affinity expressions, etc.), compute a sum by iterating through the elements of this field and subtracting \"weight\" from the sum if the node has pods which matches the corresponding podAffinityTerm; the node(s) with the highest sum are the most preferred. | [optional] |
 | **required_during_scheduling_ignored_during_execution** | [**Array<K8sIoApiCoreV1PodAffinityTerm>**](K8sIoApiCoreV1PodAffinityTerm.md) | If the anti-affinity requirements specified by this field are not met at scheduling time, the pod will not be scheduled onto the node. If the anti-affinity requirements specified by this field cease to be met at some point during pod execution (e.g. due to a pod label update), the system may or may not try to eventually evict the pod from its node. When there are multiple elements, the lists of nodes corresponding to each podAffinityTerm are intersected, i.e. all terms must be satisfied. | [optional] |
 
 ## Example

data/docs/K8sIoApimachineryPkgApisMetaV1Condition.md

@@ -0,0 +1,26 @@
+# Kubevirt::K8sIoApimachineryPkgApisMetaV1Condition
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **message** | **String** | message is a human readable message indicating details about the transition. This may be an empty string. | [default to ''] |
+| **observed_generation** | **Integer** | observedGeneration represents the .metadata.generation that the condition was set based upon. For instance, if .metadata.generation is currently 12, but the .status.conditions[x].observedGeneration is 9, the condition is out of date with respect to the current state of the instance. | [optional] |
+| **reason** | **String** | reason contains a programmatic identifier indicating the reason for the condition's last transition. Producers of specific condition types may define expected values and meanings for this field, and whether the values are considered a guaranteed API. The value should be a CamelCase string. This field may not be empty. | [default to ''] |
+| **status** | **String** | status of the condition, one of True, False, Unknown. | [default to ''] |
+| **type** | **String** | type of condition in CamelCase or in foo.example.com/CamelCase. | [default to ''] |
+
+## Example
+
+```ruby
+require 'kubevirt'
+
+instance = Kubevirt::K8sIoApimachineryPkgApisMetaV1Condition.new(
+  message: null,
+  observed_generation: null,
+  reason: null,
+  status: null,
+  type: null
+)
+```
+

data/docs/V1ChangedBlockTrackingStatus.md

@@ -4,6 +4,7 @@
 
 | Name | Type | Description | Notes |
 | ---- | ---- | ----------- | ----- |
+| **backup_status** | [**V1VirtualMachineInstanceBackupStatus**](V1VirtualMachineInstanceBackupStatus.md) |  | [optional] |
 | **state** | **String** | State represents the current CBT state | [default to ''] |
 
 ## Example
@@ -12,6 +13,7 @@
 require 'kubevirt'
 
 instance = Kubevirt::V1ChangedBlockTrackingStatus.new(
+  backup_status: null,
   state: null
 )
 ```

data/docs/V1ClaimRequest.md

@@ -0,0 +1,20 @@
+# Kubevirt::V1ClaimRequest
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **claim_name** | **String** | ClaimName references the name of an entry in the VMI's spec.resourceClaims[] array. The referenced entry may use either resourceClaimName or resourceClaimTemplateName. | [optional] |
+| **request_name** | **String** | RequestName specifies which request from the ResourceClaim/ResourceClaimTemplate spec.devices.requests array this claim request corresponds to. | [optional] |
+
+## Example
+
+```ruby
+require 'kubevirt'
+
+instance = Kubevirt::V1ClaimRequest.new(
+  claim_name: null,
+  request_name: null
+)
+```
+

data/docs/V1Condition.md

@@ -0,0 +1,24 @@
+# Kubevirt::V1Condition
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **message** | **String** |  | [optional] |
+| **reason** | **String** |  | [optional] |
+| **status** | **String** |  | [default to ''] |
+| **type** | **String** |  | [default to ''] |
+
+## Example
+
+```ruby
+require 'kubevirt'
+
+instance = Kubevirt::V1Condition.new(
+  message: null,
+  reason: null,
+  status: null,
+  type: null
+)
+```
+

data/docs/V1ConfidentialComputeConfiguration.md

@@ -0,0 +1,18 @@
+# Kubevirt::V1ConfidentialComputeConfiguration
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **tdx** | [**V1TDXConfiguration**](V1TDXConfiguration.md) |  | [optional] |
+
+## Example
+
+```ruby
+require 'kubevirt'
+
+instance = Kubevirt::V1ConfidentialComputeConfiguration.new(
+  tdx: null
+)
+```
+

data/docs/V1ContainerPathVolumeSource.md

@@ -0,0 +1,20 @@
+# Kubevirt::V1ContainerPathVolumeSource
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **path** | **String** | Path is the absolute path within the virt-launcher container to expose to the VM. The path must correspond to an existing volumeMount in the compute container. | [default to ''] |
+| **read_only** | **Boolean** | ReadOnly controls whether the volume is exposed as read-only to the VM. Defaults to true. Write access is not currently supported. | [optional] |
+
+## Example
+
+```ruby
+require 'kubevirt'
+
+instance = Kubevirt::V1ContainerPathVolumeSource.new(
+  path: null,
+  read_only: null
+)
+```
+

data/docs/V1DeveloperConfiguration.md

@@ -6,8 +6,9 @@
 | ---- | ---- | ----------- | ----- |
 | **cluster_profiler** | **Boolean** | Enable the ability to pprof profile KubeVirt control plane | [optional] |
 | **cpu_allocation_ratio** | **Integer** | For each requested virtual CPU, CPUAllocationRatio defines how much physical CPU to request per VMI from the hosting node. The value is in fraction of a CPU thread (or core on non-hyperthreaded nodes). For example, a value of 1 means 1 physical CPU thread per VMI CPU thread. A value of 100 would be 1% of a physical thread allocated for each requested VMI thread. This option has no effect on VMIs that request dedicated CPUs. More information at: https://kubevirt.io/user-guide/operations/node_overcommit/#node-cpu-allocation-ratio Defaults to 10 | [optional] |
+| **disabled_feature_gates** | **Array<String>** | DisabledFeatureGates specifies a list of experimental feature gates to disable. A feature gate must not appear in both FeatureGates and DisabledFeatureGates. | [optional] |
 | **disk_verification** | [**V1DiskVerification**](V1DiskVerification.md) |  | [optional] |
-| **feature_gates** | **Array<String>** | FeatureGates is the list of experimental features to enable. Defaults to none | [optional] |
+| **feature_gates** | **Array<String>** | FeatureGates specifies a list of experimental feature gates to enable. Defaults to none. A feature gate must not appear in both FeatureGates and DisabledFeatureGates. | [optional] |
 | **log_verbosity** | [**V1LogVerbosity**](V1LogVerbosity.md) |  | [optional] |
 | **memory_overcommit** | **Integer** | MemoryOvercommit is the percentage of memory we want to give VMIs compared to the amount given to its parent pod (virt-launcher). For example, a value of 102 means the VMI will \"see\" 2% more memory than its parent pod. Values under 100 are effectively \"undercommits\". Overcommits can lead to memory exhaustion, which in turn can lead to crashes. Use carefully. Defaults to 100 | [optional] |
 | **minimum_cluster_tsc_frequency** | **Integer** | Allow overriding the automatically determined minimum TSC frequency of the cluster and fixate the minimum to this frequency. | [optional] |
@@ -24,6 +25,7 @@ require 'kubevirt'
 instance = Kubevirt::V1DeveloperConfiguration.new(
   cluster_profiler: null,
   cpu_allocation_ratio: null,
+  disabled_feature_gates: null,
   disk_verification: null,
   feature_gates: null,
   log_verbosity: null,

data/docs/V1DomainSpec.md

@@ -15,6 +15,7 @@
 | **launch_security** | [**V1LaunchSecurity**](V1LaunchSecurity.md) |  | [optional] |
 | **machine** | [**V1Machine**](V1Machine.md) |  | [optional] |
 | **memory** | [**V1Memory**](V1Memory.md) |  | [optional] |
+| **reboot_policy** | **String** | RebootPolicy specifies how the guest should behave on reboot. Reboot (default): The guest is allowed to reboot silently. Terminate: The VMI will be terminated on guest reboot, allowing higher level controllers (such as the VM controller) to recreate the VMI with any updated configuration such as boot order changes. | [optional] |
 | **resources** | [**V1ResourceRequirements**](V1ResourceRequirements.md) |  | [optional] |
 
 ## Example
@@ -34,6 +35,7 @@ instance = Kubevirt::V1DomainSpec.new(
   launch_security: null,
   machine: null,
   memory: null,
+  reboot_policy: null,
   resources: null
 )
 ```

data/docs/V1DowntimeTuningOptions.md

@@ -0,0 +1,24 @@
+# Kubevirt::V1DowntimeTuningOptions
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **cooldown_seconds** | **Integer** | CooldownSeconds is the minimum interval in seconds between successive downtime increases. Defaults to 10. | [optional] |
+| **initial_ms** | **Integer** | InitialMs is the initial max_downtime value in milliseconds set at the start of migration. Tuning steps increase from this value. Defaults to 150. | [optional] |
+| **start_after_iteration** | **Integer** | StartAfterIteration is the memory copy iteration after which downtime tuning begins. Defaults to 3. | [optional] |
+| **steps** | **Integer** | Steps is the number of equal increments used to ramp from InitialMs to the cluster-level MaxDowntimeMs. Defaults to 7. | [optional] |
+
+## Example
+
+```ruby
+require 'kubevirt'
+
+instance = Kubevirt::V1DowntimeTuningOptions.new(
+  cooldown_seconds: null,
+  initial_ms: null,
+  start_after_iteration: null,
+  steps: null
+)
+```
+

data/docs/V1ExperimentalMigrationOptions.md

@@ -0,0 +1,22 @@
+# Kubevirt::V1ExperimentalMigrationOptions
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **compression** | **String** | Compression selects the algorithm for compressing the live migration data stream. When omitted (nil) or set to \"none\", compression is disabled. | [optional] |
+| **downtime_tuning** | [**V1DowntimeTuningOptions**](V1DowntimeTuningOptions.md) |  | [optional] |
+| **stall_detector** | [**V1StallDetectorOptions**](V1StallDetectorOptions.md) |  | [optional] |
+
+## Example
+
+```ruby
+require 'kubevirt'
+
+instance = Kubevirt::V1ExperimentalMigrationOptions.new(
+  compression: null,
+  downtime_tuning: null,
+  stall_detector: null
+)
+```
+

data/docs/V1FeatureHyperv.md

@@ -14,7 +14,7 @@
 | **spinlocks** | [**V1FeatureSpinlocks**](V1FeatureSpinlocks.md) |  | [optional] |
 | **synic** | [**V1FeatureState**](V1FeatureState.md) |  | [optional] |
 | **synictimer** | [**V1SyNICTimer**](V1SyNICTimer.md) |  | [optional] |
-| **tlbflush** | [**V1FeatureState**](V1FeatureState.md) |  | [optional] |
+| **tlbflush** | [**V1TLBFlush**](V1TLBFlush.md) |  | [optional] |
 | **vapic** | [**V1FeatureState**](V1FeatureState.md) |  | [optional] |
 | **vendorid** | [**V1FeatureVendorID**](V1FeatureVendorID.md) |  | [optional] |
 | **vpindex** | [**V1FeatureState**](V1FeatureState.md) |  | [optional] |

data/docs/V1GPU.md

@@ -4,10 +4,10 @@
 
 | Name | Type | Description | Notes |
 | ---- | ---- | ----------- | ----- |
-| **claim_name** | **String** | ClaimName needs to be provided from the list vmi.spec.resourceClaims[].name where this device is allocated | [optional] |
+| **claim_name** | **String** | ClaimName references the name of an entry in the VMI's spec.resourceClaims[] array. The referenced entry may use either resourceClaimName or resourceClaimTemplateName. | [optional] |
 | **device_name** | **String** | DeviceName is the name of the device provisioned by device-plugins | [optional] |
 | **name** | **String** | Name of the GPU device as exposed by a device plugin | [default to ''] |
-| **request_name** | **String** | RequestName needs to be provided from resourceClaim.spec.devices.requests[].name where this device is requested | [optional] |
+| **request_name** | **String** | RequestName specifies which request from the ResourceClaim/ResourceClaimTemplate spec.devices.requests array this claim request corresponds to. | [optional] |
 | **tag** | **String** | If specified, the virtual network interface address and its tag will be provided to the guest via config drive | [optional] |
 | **virtual_gpu_options** | [**V1VGPUOptions**](V1VGPUOptions.md) |  | [optional] |
 

data/docs/V1HostDevice.md

@@ -4,10 +4,10 @@
 
 | Name | Type | Description | Notes |
 | ---- | ---- | ----------- | ----- |
-| **claim_name** | **String** | ClaimName needs to be provided from the list vmi.spec.resourceClaims[].name where this device is allocated | [optional] |
+| **claim_name** | **String** | ClaimName references the name of an entry in the VMI's spec.resourceClaims[] array. The referenced entry may use either resourceClaimName or resourceClaimTemplateName. | [optional] |
 | **device_name** | **String** | DeviceName is the name of the device provisioned by device-plugins | [optional] |
 | **name** | **String** |  | [default to ''] |
-| **request_name** | **String** | RequestName needs to be provided from resourceClaim.spec.devices.requests[].name where this device is requested | [optional] |
+| **request_name** | **String** | RequestName specifies which request from the ResourceClaim/ResourceClaimTemplate spec.devices.requests array this claim request corresponds to. | [optional] |
 | **tag** | **String** | If specified, the virtual network interface address and its tag will be provided to the guest via config drive | [optional] |
 
 ## Example

data/docs/V1HypervisorConfiguration.md

@@ -0,0 +1,18 @@
+# Kubevirt::V1HypervisorConfiguration
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **name** | **String** | Name is the name of the hypervisor. Supported values are: \"kvm\", \"hyperv-direct\". | [optional] |
+
+## Example
+
+```ruby
+require 'kubevirt'
+
+instance = Kubevirt::V1HypervisorConfiguration.new(
+  name: null
+)
+```
+

data/docs/V1Interface.md

@@ -15,8 +15,10 @@
 | **model** | **String** | Interface model. One of: e1000, e1000e, igb, ne2k_pci, pcnet, rtl8139, virtio. Defaults to virtio. | [optional] |
 | **name** | **String** | Logical name of the interface as well as a reference to the associated networks. Must match the Name of a Network. | [default to ''] |
 | **passt** | **Object** | DeprecatedInterfacePasst is an alias to the deprecated InterfacePasst Deprecated: Removed in v1.3 | [optional] |
+| **passt_binding** | **Object** | InterfacePasstBinding connects to a given network using passt usermode networking. | [optional] |
 | **pci_address** | **String** | If specified, the virtual network interface will be placed on the guests pci address with the specified PCI address. For example: 0000:81:01.10 | [optional] |
-| **ports** | [**Array<V1Port>**](V1Port.md) | List of ports to be forwarded to the virtual machine. | [optional] |
+| **port_ranges** | [**Array<V1PortRange>**](V1PortRange.md) | List of port ranges to be forwarded to the virtual machine. Mutually exclusive with ports. Only supported on masquerade interfaces. This feature is in Alpha. | [optional] |
+| **ports** | [**Array<V1Port>**](V1Port.md) | List of ports to be forwarded to the virtual machine. Mutually exclusive with portRanges. | [optional] |
 | **slirp** | **Object** | DeprecatedInterfaceSlirp is an alias to the deprecated InterfaceSlirp that connects to a given network using QEMU user networking mode. Deprecated: Removed in v1.3 | [optional] |
 | **sriov** | **Object** | InterfaceSRIOV connects to a given network by passing-through an SR-IOV PCI device via vfio. | [optional] |
 | **state** | **String** | State represents the requested operational state of the interface. The supported values are: `absent`, expressing a request to remove the interface. `down`, expressing a request to set the link down. `up`, expressing a request to set the link up. Empty value functions as `up`. | [optional] |
@@ -39,7 +41,9 @@ instance = Kubevirt::V1Interface.new(
   model: null,
   name: null,
   passt: null,
+  passt_binding: null,
   pci_address: null,
+  port_ranges: null,
   ports: null,
   slirp: null,
   sriov: null,

data/docs/V1KubeVirtConfiguration.md

@@ -10,6 +10,7 @@
 | **auto_cpu_limit_namespace_label_selector** | [**K8sIoApimachineryPkgApisMetaV1LabelSelector**](K8sIoApimachineryPkgApisMetaV1LabelSelector.md) |  | [optional] |
 | **changed_block_tracking_label_selectors** | [**V1ChangedBlockTrackingSelectors**](V1ChangedBlockTrackingSelectors.md) |  | [optional] |
 | **common_instancetypes_deployment** | [**V1CommonInstancetypesDeployment**](V1CommonInstancetypesDeployment.md) |  | [optional] |
+| **confidential_compute** | [**V1ConfidentialComputeConfiguration**](V1ConfidentialComputeConfiguration.md) |  | [optional] |
 | **controller_configuration** | [**V1ReloadableComponentConfiguration**](V1ReloadableComponentConfiguration.md) |  | [optional] |
 | **cpu_model** | **String** |  | [optional] |
 | **cpu_request** | **Object** | Quantity is a fixed-point representation of a number. It provides convenient marshaling/unmarshaling in JSON and YAML, in addition to String() and AsInt64() accessors.  The serialization format is:  ``` <quantity>        ::= <signedNumber><suffix>   (Note that <suffix> may be empty, from the \"\" case in <decimalSI>.)  <digit>           ::= 0 | 1 | ... | 9 <digits>          ::= <digit> | <digit><digits> <number>          ::= <digits> | <digits>.<digits> | <digits>. | .<digits> <sign>            ::= \"+\" | \"-\" <signedNumber>    ::= <number> | <sign><number> <suffix>          ::= <binarySI> | <decimalExponent> | <decimalSI> <binarySI>        ::= Ki | Mi | Gi | Ti | Pi | Ei   (International System of units; See: http://physics.nist.gov/cuu/Units/binary.html)  <decimalSI>       ::= m | \"\" | k | M | G | T | P | E   (Note that 1024 = 1Ki but 1000 = 1k; I didn't choose the capitalization.)  <decimalExponent> ::= \"e\" <signedNumber> | \"E\" <signedNumber> ```  No matter which of the three exponent forms is used, no quantity may represent a number greater than 2^63-1 in magnitude, nor may it have more than 3 decimal places. Numbers larger or more precise will be capped or rounded up. (E.g.: 0.1m will rounded up to 1m.) This may be extended in the future if we require larger or smaller quantities.  When a Quantity is parsed from a string, it will remember the type of suffix it had, and will use the same type again when it is serialized.  Before serializing, Quantity will be put in \"canonical form\". This means that Exponent/suffix will be adjusted up or down (with a corresponding increase or decrease in Mantissa) such that:  - No precision is lost - No fractional digits will be emitted - The exponent (or suffix) is as large as possible.  The sign will be omitted unless the number is negative.  Examples:  - 1.5 will be serialized as \"1500m\" - 1.5Gi will be serialized as \"1536Mi\"  Note that the quantity will NEVER be internally represented by a floating point number. That is the whole point of this exercise.  Non-canonical values will still parse as long as they are well formed, but will be re-emitted in their canonical form. (So always use canonical form, or don't diff.)  This format is intended to make it difficult to use these numbers without writing some sort of special handling code in the hopes that that will cause implementors to also use a fixed point implementation. | [optional] |
@@ -18,7 +19,8 @@
 | **emulated_machines** | **Array<String>** | Deprecated. Use architectureConfiguration instead. | [optional] |
 | **eviction_strategy** | **String** | EvictionStrategy defines at the cluster level if the VirtualMachineInstance should be migrated instead of shut-off in case of a node drain. If the VirtualMachineInstance specific field is set it overrides the cluster level one. | [optional] |
 | **handler_configuration** | [**V1ReloadableComponentConfiguration**](V1ReloadableComponentConfiguration.md) |  | [optional] |
-| **image_pull_policy** | **String** | Possible enum values:  - `\"Always\"` means that kubelet always attempts to pull the latest image. Container will fail If the pull fails.  - `\"IfNotPresent\"` means that kubelet pulls if the image isn't present on disk. Container will fail if the image isn't present and the pull fails.  - `\"Never\"` means that kubelet never pulls an image, but only uses a local image. Container will fail if the image isn't present | [optional] |
+| **hypervisors** | [**Array<V1HypervisorConfiguration>**](V1HypervisorConfiguration.md) | Hypervisors holds information regarding the hypervisor configurations supported on this cluster. | [optional] |
+| **image_pull_policy** | **String** | The ImagePullPolicy to use for user workload pods and their containers (launcher pods, exporter pods, etc.). For KubeVirt infrastructure images, use spec.imagePullPolicy instead.  Possible enum values:  - `\"Always\"` means that kubelet always attempts to pull the latest image. Container will fail If the pull fails.  - `\"IfNotPresent\"` means that kubelet pulls if the image isn't present on disk. Container will fail if the image isn't present and the pull fails.  - `\"Never\"` means that kubelet never pulls an image, but only uses a local image. Container will fail if the image isn't present | [optional] |
 | **instancetype** | [**V1InstancetypeConfiguration**](V1InstancetypeConfiguration.md) |  | [optional] |
 | **ksm_configuration** | [**V1KSMConfiguration**](V1KSMConfiguration.md) |  | [optional] |
 | **live_update_configuration** | [**V1LiveUpdateConfiguration**](V1LiveUpdateConfiguration.md) |  | [optional] |
@@ -31,12 +33,15 @@
 | **obsolete_cpu_models** | **Hash<String, Boolean>** |  | [optional] |
 | **ovmf_path** | **String** | Deprecated. Use architectureConfiguration instead. | [optional] |
 | **permitted_host_devices** | [**V1PermittedHostDevices**](V1PermittedHostDevices.md) |  | [optional] |
+| **persistent_reservation_configuration** | [**V1PersistentReservationConfiguration**](V1PersistentReservationConfiguration.md) |  | [optional] |
+| **role_aggregation_strategy** | **String** | 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 RoleAggregationStrategy to \"Manual\" requires the OptOutRoleAggregation feature gate to be enabled (Beta, enabled by default since v1.9.0). | [optional] |
 | **seccomp_configuration** | [**V1SeccompConfiguration**](V1SeccompConfiguration.md) |  | [optional] |
 | **selinux_launcher_type** | **String** |  | [optional] |
 | **smbios** | [**V1SMBiosConfiguration**](V1SMBiosConfiguration.md) |  | [optional] |
 | **support_container_resources** | [**Array<V1SupportContainerResources>**](V1SupportContainerResources.md) | SupportContainerResources specifies the resource requirements for various types of supporting containers such as container disks/virtiofs/sidecars and hotplug attachment pods. If omitted a sensible default will be supplied. | [optional] |
 | **supported_guest_agent_versions** | **Array<String>** | deprecated | [optional] |
 | **tls_configuration** | [**V1TLSConfiguration**](V1TLSConfiguration.md) |  | [optional] |
+| **virt_template_deployment** | [**V1VirtTemplateDeployment**](V1VirtTemplateDeployment.md) |  | [optional] |
 | **virtual_machine_instances_per_node** | **Integer** |  | [optional] |
 | **virtual_machine_options** | [**V1VirtualMachineOptions**](V1VirtualMachineOptions.md) |  | [optional] |
 | **vm_rollout_strategy** | **String** | VMRolloutStrategy defines how live-updatable fields, like CPU sockets, memory, tolerations, and affinity, are propagated from a VM to its VMI. | [optional] |
@@ -55,6 +60,7 @@ instance = Kubevirt::V1KubeVirtConfiguration.new(
   auto_cpu_limit_namespace_label_selector: null,
   changed_block_tracking_label_selectors: null,
   common_instancetypes_deployment: null,
+  confidential_compute: null,
   controller_configuration: null,
   cpu_model: null,
   cpu_request: null,
@@ -63,6 +69,7 @@ instance = Kubevirt::V1KubeVirtConfiguration.new(
   emulated_machines: null,
   eviction_strategy: null,
   handler_configuration: null,
+  hypervisors: null,
   image_pull_policy: null,
   instancetype: null,
   ksm_configuration: null,
@@ -76,12 +83,15 @@ instance = Kubevirt::V1KubeVirtConfiguration.new(
   obsolete_cpu_models: null,
   ovmf_path: null,
   permitted_host_devices: null,
+  persistent_reservation_configuration: null,
+  role_aggregation_strategy: null,
   seccomp_configuration: null,
   selinux_launcher_type: null,
   smbios: null,
   support_container_resources: null,
   supported_guest_agent_versions: null,
   tls_configuration: null,
+  virt_template_deployment: null,
   virtual_machine_instances_per_node: null,
   virtual_machine_options: null,
   vm_rollout_strategy: null,

data/docs/V1KubeVirtSpec.md

@@ -7,7 +7,7 @@
 | **certificate_rotate_strategy** | [**V1KubeVirtCertificateRotateStrategy**](V1KubeVirtCertificateRotateStrategy.md) |  | [optional] |
 | **configuration** | [**V1KubeVirtConfiguration**](V1KubeVirtConfiguration.md) |  | [optional] |
 | **customize_components** | [**V1CustomizeComponents**](V1CustomizeComponents.md) |  | [optional] |
-| **image_pull_policy** | **String** | The ImagePullPolicy to use.  Possible enum values:  - `\"Always\"` means that kubelet always attempts to pull the latest image. Container will fail If the pull fails.  - `\"IfNotPresent\"` means that kubelet pulls if the image isn't present on disk. Container will fail if the image isn't present and the pull fails.  - `\"Never\"` means that kubelet never pulls an image, but only uses a local image. Container will fail if the image isn't present | [optional] |
+| **image_pull_policy** | **String** | The ImagePullPolicy to use for KubeVirt operator-managed infrastructure images (virt-api, virt-controller, virt-handler, virt-exportproxy, etc.). For pull policy of user workload pods, see spec.configuration.imagePullPolicy.  Possible enum values:  - `\"Always\"` means that kubelet always attempts to pull the latest image. Container will fail If the pull fails.  - `\"IfNotPresent\"` means that kubelet pulls if the image isn't present on disk. Container will fail if the image isn't present and the pull fails.  - `\"Never\"` means that kubelet never pulls an image, but only uses a local image. Container will fail if the image isn't present | [optional] |
 | **image_pull_secrets** | [**Array<K8sIoApiCoreV1LocalObjectReference>**](K8sIoApiCoreV1LocalObjectReference.md) | The imagePullSecrets to pull the container images from Defaults to none | [optional] |
 | **image_registry** | **String** | The image registry to pull the container images from Defaults to the same registry the operator's container image is pulled from. | [optional] |
 | **image_tag** | **String** | The image tag to use for the continer images installed. Defaults to the same tag as the operator's container image. | [optional] |

data/docs/V1MediatedDevicesConfiguration.md

@@ -4,6 +4,7 @@
 
 | Name | Type | Description | Notes |
 | ---- | ---- | ----------- | ----- |
+| **enabled** | **Boolean** | Enable the creation and removal of mediated devices by virt-handler Replaces the deprecated DisableMDEVConfiguration feature gate Defaults to true | [optional] |
 | **mediated_device_types** | **Array<String>** |  | [optional] |
 | **mediated_devices_types** | **Array<String>** | Deprecated. Use mediatedDeviceTypes instead. | [optional] |
 | **node_mediated_device_types** | [**Array<V1NodeMediatedDeviceTypesConfig>**](V1NodeMediatedDeviceTypesConfig.md) |  | [optional] |
@@ -14,6 +15,7 @@
 require 'kubevirt'
 
 instance = Kubevirt::V1MediatedDevicesConfiguration.new(
+  enabled: null,
   mediated_device_types: null,
   mediated_devices_types: null,
   node_mediated_device_types: null

data/docs/V1Memory.md

@@ -7,6 +7,7 @@
 | **guest** | **Object** | Quantity is a fixed-point representation of a number. It provides convenient marshaling/unmarshaling in JSON and YAML, in addition to String() and AsInt64() accessors.  The serialization format is:  ``` <quantity>        ::= <signedNumber><suffix>   (Note that <suffix> may be empty, from the \"\" case in <decimalSI>.)  <digit>           ::= 0 | 1 | ... | 9 <digits>          ::= <digit> | <digit><digits> <number>          ::= <digits> | <digits>.<digits> | <digits>. | .<digits> <sign>            ::= \"+\" | \"-\" <signedNumber>    ::= <number> | <sign><number> <suffix>          ::= <binarySI> | <decimalExponent> | <decimalSI> <binarySI>        ::= Ki | Mi | Gi | Ti | Pi | Ei   (International System of units; See: http://physics.nist.gov/cuu/Units/binary.html)  <decimalSI>       ::= m | \"\" | k | M | G | T | P | E   (Note that 1024 = 1Ki but 1000 = 1k; I didn't choose the capitalization.)  <decimalExponent> ::= \"e\" <signedNumber> | \"E\" <signedNumber> ```  No matter which of the three exponent forms is used, no quantity may represent a number greater than 2^63-1 in magnitude, nor may it have more than 3 decimal places. Numbers larger or more precise will be capped or rounded up. (E.g.: 0.1m will rounded up to 1m.) This may be extended in the future if we require larger or smaller quantities.  When a Quantity is parsed from a string, it will remember the type of suffix it had, and will use the same type again when it is serialized.  Before serializing, Quantity will be put in \"canonical form\". This means that Exponent/suffix will be adjusted up or down (with a corresponding increase or decrease in Mantissa) such that:  - No precision is lost - No fractional digits will be emitted - The exponent (or suffix) is as large as possible.  The sign will be omitted unless the number is negative.  Examples:  - 1.5 will be serialized as \"1500m\" - 1.5Gi will be serialized as \"1536Mi\"  Note that the quantity will NEVER be internally represented by a floating point number. That is the whole point of this exercise.  Non-canonical values will still parse as long as they are well formed, but will be re-emitted in their canonical form. (So always use canonical form, or don't diff.)  This format is intended to make it difficult to use these numbers without writing some sort of special handling code in the hopes that that will cause implementors to also use a fixed point implementation. | [optional] |
 | **hugepages** | [**V1Hugepages**](V1Hugepages.md) |  | [optional] |
 | **max_guest** | **Object** | Quantity is a fixed-point representation of a number. It provides convenient marshaling/unmarshaling in JSON and YAML, in addition to String() and AsInt64() accessors.  The serialization format is:  ``` <quantity>        ::= <signedNumber><suffix>   (Note that <suffix> may be empty, from the \"\" case in <decimalSI>.)  <digit>           ::= 0 | 1 | ... | 9 <digits>          ::= <digit> | <digit><digits> <number>          ::= <digits> | <digits>.<digits> | <digits>. | .<digits> <sign>            ::= \"+\" | \"-\" <signedNumber>    ::= <number> | <sign><number> <suffix>          ::= <binarySI> | <decimalExponent> | <decimalSI> <binarySI>        ::= Ki | Mi | Gi | Ti | Pi | Ei   (International System of units; See: http://physics.nist.gov/cuu/Units/binary.html)  <decimalSI>       ::= m | \"\" | k | M | G | T | P | E   (Note that 1024 = 1Ki but 1000 = 1k; I didn't choose the capitalization.)  <decimalExponent> ::= \"e\" <signedNumber> | \"E\" <signedNumber> ```  No matter which of the three exponent forms is used, no quantity may represent a number greater than 2^63-1 in magnitude, nor may it have more than 3 decimal places. Numbers larger or more precise will be capped or rounded up. (E.g.: 0.1m will rounded up to 1m.) This may be extended in the future if we require larger or smaller quantities.  When a Quantity is parsed from a string, it will remember the type of suffix it had, and will use the same type again when it is serialized.  Before serializing, Quantity will be put in \"canonical form\". This means that Exponent/suffix will be adjusted up or down (with a corresponding increase or decrease in Mantissa) such that:  - No precision is lost - No fractional digits will be emitted - The exponent (or suffix) is as large as possible.  The sign will be omitted unless the number is negative.  Examples:  - 1.5 will be serialized as \"1500m\" - 1.5Gi will be serialized as \"1536Mi\"  Note that the quantity will NEVER be internally represented by a floating point number. That is the whole point of this exercise.  Non-canonical values will still parse as long as they are well formed, but will be re-emitted in their canonical form. (So always use canonical form, or don't diff.)  This format is intended to make it difficult to use these numbers without writing some sort of special handling code in the hopes that that will cause implementors to also use a fixed point implementation. | [optional] |
+| **reserved_overhead** | [**V1ReservedOverhead**](V1ReservedOverhead.md) |  | [optional] |
 
 ## Example
 
@@ -16,7 +17,8 @@ require 'kubevirt'
 instance = Kubevirt::V1Memory.new(
   guest: null,
   hugepages: null,
-  max_guest: null
+  max_guest: null,
+  reserved_overhead: null
 )
 ```
 

data/docs/V1MemoryStatus.md

@@ -7,6 +7,7 @@
 | **guest_at_boot** | **Object** | Quantity is a fixed-point representation of a number. It provides convenient marshaling/unmarshaling in JSON and YAML, in addition to String() and AsInt64() accessors.  The serialization format is:  ``` <quantity>        ::= <signedNumber><suffix>   (Note that <suffix> may be empty, from the \"\" case in <decimalSI>.)  <digit>           ::= 0 | 1 | ... | 9 <digits>          ::= <digit> | <digit><digits> <number>          ::= <digits> | <digits>.<digits> | <digits>. | .<digits> <sign>            ::= \"+\" | \"-\" <signedNumber>    ::= <number> | <sign><number> <suffix>          ::= <binarySI> | <decimalExponent> | <decimalSI> <binarySI>        ::= Ki | Mi | Gi | Ti | Pi | Ei   (International System of units; See: http://physics.nist.gov/cuu/Units/binary.html)  <decimalSI>       ::= m | \"\" | k | M | G | T | P | E   (Note that 1024 = 1Ki but 1000 = 1k; I didn't choose the capitalization.)  <decimalExponent> ::= \"e\" <signedNumber> | \"E\" <signedNumber> ```  No matter which of the three exponent forms is used, no quantity may represent a number greater than 2^63-1 in magnitude, nor may it have more than 3 decimal places. Numbers larger or more precise will be capped or rounded up. (E.g.: 0.1m will rounded up to 1m.) This may be extended in the future if we require larger or smaller quantities.  When a Quantity is parsed from a string, it will remember the type of suffix it had, and will use the same type again when it is serialized.  Before serializing, Quantity will be put in \"canonical form\". This means that Exponent/suffix will be adjusted up or down (with a corresponding increase or decrease in Mantissa) such that:  - No precision is lost - No fractional digits will be emitted - The exponent (or suffix) is as large as possible.  The sign will be omitted unless the number is negative.  Examples:  - 1.5 will be serialized as \"1500m\" - 1.5Gi will be serialized as \"1536Mi\"  Note that the quantity will NEVER be internally represented by a floating point number. That is the whole point of this exercise.  Non-canonical values will still parse as long as they are well formed, but will be re-emitted in their canonical form. (So always use canonical form, or don't diff.)  This format is intended to make it difficult to use these numbers without writing some sort of special handling code in the hopes that that will cause implementors to also use a fixed point implementation. | [optional] |
 | **guest_current** | **Object** | Quantity is a fixed-point representation of a number. It provides convenient marshaling/unmarshaling in JSON and YAML, in addition to String() and AsInt64() accessors.  The serialization format is:  ``` <quantity>        ::= <signedNumber><suffix>   (Note that <suffix> may be empty, from the \"\" case in <decimalSI>.)  <digit>           ::= 0 | 1 | ... | 9 <digits>          ::= <digit> | <digit><digits> <number>          ::= <digits> | <digits>.<digits> | <digits>. | .<digits> <sign>            ::= \"+\" | \"-\" <signedNumber>    ::= <number> | <sign><number> <suffix>          ::= <binarySI> | <decimalExponent> | <decimalSI> <binarySI>        ::= Ki | Mi | Gi | Ti | Pi | Ei   (International System of units; See: http://physics.nist.gov/cuu/Units/binary.html)  <decimalSI>       ::= m | \"\" | k | M | G | T | P | E   (Note that 1024 = 1Ki but 1000 = 1k; I didn't choose the capitalization.)  <decimalExponent> ::= \"e\" <signedNumber> | \"E\" <signedNumber> ```  No matter which of the three exponent forms is used, no quantity may represent a number greater than 2^63-1 in magnitude, nor may it have more than 3 decimal places. Numbers larger or more precise will be capped or rounded up. (E.g.: 0.1m will rounded up to 1m.) This may be extended in the future if we require larger or smaller quantities.  When a Quantity is parsed from a string, it will remember the type of suffix it had, and will use the same type again when it is serialized.  Before serializing, Quantity will be put in \"canonical form\". This means that Exponent/suffix will be adjusted up or down (with a corresponding increase or decrease in Mantissa) such that:  - No precision is lost - No fractional digits will be emitted - The exponent (or suffix) is as large as possible.  The sign will be omitted unless the number is negative.  Examples:  - 1.5 will be serialized as \"1500m\" - 1.5Gi will be serialized as \"1536Mi\"  Note that the quantity will NEVER be internally represented by a floating point number. That is the whole point of this exercise.  Non-canonical values will still parse as long as they are well formed, but will be re-emitted in their canonical form. (So always use canonical form, or don't diff.)  This format is intended to make it difficult to use these numbers without writing some sort of special handling code in the hopes that that will cause implementors to also use a fixed point implementation. | [optional] |
 | **guest_requested** | **Object** | Quantity is a fixed-point representation of a number. It provides convenient marshaling/unmarshaling in JSON and YAML, in addition to String() and AsInt64() accessors.  The serialization format is:  ``` <quantity>        ::= <signedNumber><suffix>   (Note that <suffix> may be empty, from the \"\" case in <decimalSI>.)  <digit>           ::= 0 | 1 | ... | 9 <digits>          ::= <digit> | <digit><digits> <number>          ::= <digits> | <digits>.<digits> | <digits>. | .<digits> <sign>            ::= \"+\" | \"-\" <signedNumber>    ::= <number> | <sign><number> <suffix>          ::= <binarySI> | <decimalExponent> | <decimalSI> <binarySI>        ::= Ki | Mi | Gi | Ti | Pi | Ei   (International System of units; See: http://physics.nist.gov/cuu/Units/binary.html)  <decimalSI>       ::= m | \"\" | k | M | G | T | P | E   (Note that 1024 = 1Ki but 1000 = 1k; I didn't choose the capitalization.)  <decimalExponent> ::= \"e\" <signedNumber> | \"E\" <signedNumber> ```  No matter which of the three exponent forms is used, no quantity may represent a number greater than 2^63-1 in magnitude, nor may it have more than 3 decimal places. Numbers larger or more precise will be capped or rounded up. (E.g.: 0.1m will rounded up to 1m.) This may be extended in the future if we require larger or smaller quantities.  When a Quantity is parsed from a string, it will remember the type of suffix it had, and will use the same type again when it is serialized.  Before serializing, Quantity will be put in \"canonical form\". This means that Exponent/suffix will be adjusted up or down (with a corresponding increase or decrease in Mantissa) such that:  - No precision is lost - No fractional digits will be emitted - The exponent (or suffix) is as large as possible.  The sign will be omitted unless the number is negative.  Examples:  - 1.5 will be serialized as \"1500m\" - 1.5Gi will be serialized as \"1536Mi\"  Note that the quantity will NEVER be internally represented by a floating point number. That is the whole point of this exercise.  Non-canonical values will still parse as long as they are well formed, but will be re-emitted in their canonical form. (So always use canonical form, or don't diff.)  This format is intended to make it difficult to use these numbers without writing some sort of special handling code in the hopes that that will cause implementors to also use a fixed point implementation. | [optional] |
+| **memory_overhead** | **Object** | Quantity is a fixed-point representation of a number. It provides convenient marshaling/unmarshaling in JSON and YAML, in addition to String() and AsInt64() accessors.  The serialization format is:  ``` <quantity>        ::= <signedNumber><suffix>   (Note that <suffix> may be empty, from the \"\" case in <decimalSI>.)  <digit>           ::= 0 | 1 | ... | 9 <digits>          ::= <digit> | <digit><digits> <number>          ::= <digits> | <digits>.<digits> | <digits>. | .<digits> <sign>            ::= \"+\" | \"-\" <signedNumber>    ::= <number> | <sign><number> <suffix>          ::= <binarySI> | <decimalExponent> | <decimalSI> <binarySI>        ::= Ki | Mi | Gi | Ti | Pi | Ei   (International System of units; See: http://physics.nist.gov/cuu/Units/binary.html)  <decimalSI>       ::= m | \"\" | k | M | G | T | P | E   (Note that 1024 = 1Ki but 1000 = 1k; I didn't choose the capitalization.)  <decimalExponent> ::= \"e\" <signedNumber> | \"E\" <signedNumber> ```  No matter which of the three exponent forms is used, no quantity may represent a number greater than 2^63-1 in magnitude, nor may it have more than 3 decimal places. Numbers larger or more precise will be capped or rounded up. (E.g.: 0.1m will rounded up to 1m.) This may be extended in the future if we require larger or smaller quantities.  When a Quantity is parsed from a string, it will remember the type of suffix it had, and will use the same type again when it is serialized.  Before serializing, Quantity will be put in \"canonical form\". This means that Exponent/suffix will be adjusted up or down (with a corresponding increase or decrease in Mantissa) such that:  - No precision is lost - No fractional digits will be emitted - The exponent (or suffix) is as large as possible.  The sign will be omitted unless the number is negative.  Examples:  - 1.5 will be serialized as \"1500m\" - 1.5Gi will be serialized as \"1536Mi\"  Note that the quantity will NEVER be internally represented by a floating point number. That is the whole point of this exercise.  Non-canonical values will still parse as long as they are well formed, but will be re-emitted in their canonical form. (So always use canonical form, or don't diff.)  This format is intended to make it difficult to use these numbers without writing some sort of special handling code in the hopes that that will cause implementors to also use a fixed point implementation. | [optional] |
 
 ## Example
 
@@ -16,7 +17,8 @@ require 'kubevirt'
 instance = Kubevirt::V1MemoryStatus.new(
   guest_at_boot: null,
   guest_current: null,
-  guest_requested: null
+  guest_requested: null,
+  memory_overhead: null
 )
 ```
 

data/docs/V1MigrationConfiguration.md

@@ -11,12 +11,14 @@
 | **completion_timeout_per_gi_b** | **Integer** | CompletionTimeoutPerGiB is the maximum number of seconds per GiB a migration is allowed to take. If the timeout is reached, the migration will be either paused, switched to post-copy or cancelled depending on other settings. Defaults to 150 | [optional] |
 | **disable_tls** | **Boolean** | When set to true, DisableTLS will disable the additional layer of live migration encryption provided by KubeVirt. This is usually a bad idea. Defaults to false | [optional] |
 | **match_se_linux_level_on_migration** | **Boolean** | By default, the SELinux level of target virt-launcher pods is forced to the level of the source virt-launcher. When set to true, MatchSELinuxLevelOnMigration lets the CRI auto-assign a random level to the target. That will ensure the target virt-launcher doesn't share categories with another pod on the node. However, migrations will fail when using RWX volumes that don't automatically deal with SELinux levels. | [optional] |
+| **max_downtime_ms** | **Integer** | MaxDowntimeMs specifies the maximum tolerable downtime (in milliseconds) during switchover. Defaults to 900 | [optional] |
 | **network** | **String** | Network is the name of the CNI network to use for live migrations. By default, migrations go through the pod network. | [optional] |
 | **node_drain_taint_key** | **String** | NodeDrainTaintKey defines the taint key that indicates a node should be drained. Note: this option relies on the deprecated node taint feature. Default: kubevirt.io/drain | [optional] |
 | **parallel_migrations_per_cluster** | **Integer** | ParallelMigrationsPerCluster is the total number of concurrent live migrations allowed cluster-wide. Defaults to 5 | [optional] |
 | **parallel_outbound_migrations_per_node** | **Integer** | ParallelOutboundMigrationsPerNode is the maximum number of concurrent outgoing live migrations allowed per node. Defaults to 2 | [optional] |
 | **progress_timeout** | **Integer** | ProgressTimeout is the maximum number of seconds a live migration is allowed to make no progress. Hitting this timeout means a migration transferred 0 data for that many seconds. The migration is then considered stuck and therefore cancelled. Defaults to 150 | [optional] |
 | **unsafe_migration_override** | **Boolean** | UnsafeMigrationOverride allows live migrations to occur even if the compatibility check indicates the migration will be unsafe to the guest. Defaults to false | [optional] |
+| **utility_volumes_timeout** | **Integer** | UtilityVolumesTimeout is the maximum number of seconds a migration can wait in Pending state for utility volumes to be detached. If utility volumes are still present after this timeout, the migration will be marked as Failed. Defaults to 150 | [optional] |
 
 ## Example
 
@@ -31,12 +33,14 @@ instance = Kubevirt::V1MigrationConfiguration.new(
   completion_timeout_per_gi_b: null,
   disable_tls: null,
   match_se_linux_level_on_migration: null,
+  max_downtime_ms: null,
   network: null,
   node_drain_taint_key: null,
   parallel_migrations_per_cluster: null,
   parallel_outbound_migrations_per_node: null,
   progress_timeout: null,
-  unsafe_migration_override: null
+  unsafe_migration_override: null,
+  utility_volumes_timeout: null
 )
 ```
 

data/docs/V1Network.md

@@ -7,6 +7,7 @@
 | **multus** | [**V1MultusNetwork**](V1MultusNetwork.md) |  | [optional] |
 | **name** | **String** | Network name. Must be a DNS_LABEL and unique within the vm. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names | [default to ''] |
 | **pod** | [**V1PodNetwork**](V1PodNetwork.md) |  | [optional] |
+| **resource_claim** | [**V1ClaimRequest**](V1ClaimRequest.md) |  | [optional] |
 
 ## Example
 
@@ -16,7 +17,8 @@ require 'kubevirt'
 instance = Kubevirt::V1Network.new(
   multus: null,
   name: null,
-  pod: null
+  pod: null,
+  resource_claim: null
 )
 ```
 

data/docs/V1PersistentReservationConfiguration.md

@@ -0,0 +1,18 @@
+# Kubevirt::V1PersistentReservationConfiguration
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **enabled** | **Boolean** | 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. | [optional] |
+
+## Example
+
+```ruby
+require 'kubevirt'
+
+instance = Kubevirt::V1PersistentReservationConfiguration.new(
+  enabled: null
+)
+```
+

data/docs/V1PortRange.md

@@ -0,0 +1,22 @@
+# Kubevirt::V1PortRange
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **_end** | **Integer** | Last port of the range to expose for the virtual machine. This must be a valid port number, 0 < x < 65536. Must be greater than or equal to start. | [default to 0] |
+| **protocol** | **String** | Required. Must be UDP or TCP. | [default to ''] |
+| **start** | **Integer** | First port of the range to expose for the virtual machine. This must be a valid port number, 0 < x < 65536. | [default to 0] |
+
+## Example
+
+```ruby
+require 'kubevirt'
+
+instance = Kubevirt::V1PortRange.new(
+  _end: null,
+  protocol: null,
+  start: null
+)
+```
+