kubevirt 0.1.0 → 0.2.1

data/docs/K8sIoApiCoreV1PodAffinityTerm.md

@@ -5,8 +5,8 @@
 | Name | Type | Description | Notes |
 | ---- | ---- | ----------- | ----- |
 | **label_selector** | [**K8sIoApimachineryPkgApisMetaV1LabelSelector**](K8sIoApimachineryPkgApisMetaV1LabelSelector.md) |  | [optional] |
-| **match_label_keys** | **Array<String>** | MatchLabelKeys is a set of pod label keys to select which pods will be taken into consideration. The keys are used to lookup values from the incoming pod labels, those key-value labels are merged with `labelSelector` as `key in (value)` to select the group of existing pods which pods will be taken into consideration for the incoming pod's pod (anti) affinity. Keys that don't exist in the incoming pod labels will be ignored. The default value is empty. The same key is forbidden to exist in both matchLabelKeys and labelSelector. Also, matchLabelKeys cannot be set when labelSelector isn't set. This is a beta field and requires enabling MatchLabelKeysInPodAffinity feature gate (enabled by default). | [optional] |
-| **mismatch_label_keys** | **Array<String>** | MismatchLabelKeys is a set of pod label keys to select which pods will be taken into consideration. The keys are used to lookup values from the incoming pod labels, those key-value labels are merged with `labelSelector` as `key notin (value)` to select the group of existing pods which pods will be taken into consideration for the incoming pod's pod (anti) affinity. Keys that don't exist in the incoming pod labels will be ignored. The default value is empty. The same key is forbidden to exist in both mismatchLabelKeys and labelSelector. Also, mismatchLabelKeys cannot be set when labelSelector isn't set. This is a beta field and requires enabling MatchLabelKeysInPodAffinity feature gate (enabled by default). | [optional] |
+| **match_label_keys** | **Array<String>** | MatchLabelKeys is a set of pod label keys to select which pods will be taken into consideration. The keys are used to lookup values from the incoming pod labels, those key-value labels are merged with `labelSelector` as `key in (value)` to select the group of existing pods which pods will be taken into consideration for the incoming pod's pod (anti) affinity. Keys that don't exist in the incoming pod labels will be ignored. The default value is empty. The same key is forbidden to exist in both matchLabelKeys and labelSelector. Also, matchLabelKeys cannot be set when labelSelector isn't set. | [optional] |
+| **mismatch_label_keys** | **Array<String>** | MismatchLabelKeys is a set of pod label keys to select which pods will be taken into consideration. The keys are used to lookup values from the incoming pod labels, those key-value labels are merged with `labelSelector` as `key notin (value)` to select the group of existing pods which pods will be taken into consideration for the incoming pod's pod (anti) affinity. Keys that don't exist in the incoming pod labels will be ignored. The default value is empty. The same key is forbidden to exist in both mismatchLabelKeys and labelSelector. Also, mismatchLabelKeys cannot be set when labelSelector isn't set. | [optional] |
 | **namespace_selector** | [**K8sIoApimachineryPkgApisMetaV1LabelSelector**](K8sIoApimachineryPkgApisMetaV1LabelSelector.md) |  | [optional] |
 | **namespaces** | **Array<String>** | namespaces specifies a static list of namespace names that the term applies to. The term is applied to the union of the namespaces listed in this field and the ones selected by namespaceSelector. null or empty namespaces list and null namespaceSelector means \"this pod's namespace\". | [optional] |
 | **topology_key** | **String** | This pod should be co-located (affinity) or not co-located (anti-affinity) with the pods matching the labelSelector in the specified namespaces, where co-located is defined as running on a node whose value of the label with key topologyKey matches that of any node on which any of the selected pods is running. Empty topologyKey is not allowed. | [default to ''] |

data/docs/K8sIoApiCoreV1PodDNSConfigOption.md

@@ -4,8 +4,8 @@
 
 | Name | Type | Description | Notes |
 | ---- | ---- | ----------- | ----- |
-| **name** | **String** | Required. | [optional] |
-| **value** | **String** |  | [optional] |
+| **name** | **String** | Name is this DNS resolver option's name. Required. | [optional] |
+| **value** | **String** | Value is this DNS resolver option's value. | [optional] |
 
 ## Example
 

data/docs/K8sIoApiCoreV1PodResourceClaim.md

@@ -0,0 +1,22 @@
+# Kubevirt::K8sIoApiCoreV1PodResourceClaim
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **name** | **String** | Name uniquely identifies this resource claim inside the pod. This must be a DNS_LABEL. | [default to ''] |
+| **resource_claim_name** | **String** | ResourceClaimName is the name of a ResourceClaim object in the same namespace as this pod.  Exactly one of ResourceClaimName and ResourceClaimTemplateName must be set. | [optional] |
+| **resource_claim_template_name** | **String** | ResourceClaimTemplateName is the name of a ResourceClaimTemplate object in the same namespace as this pod.  The template will be used to create a new ResourceClaim, which will be bound to this pod. When this pod is deleted, the ResourceClaim will also be deleted. The pod name and resource name, along with a generated component, will be used to form a unique name for the ResourceClaim, which will be recorded in pod.status.resourceClaimStatuses.  This field is immutable and no changes will be made to the corresponding ResourceClaim by the control plane after creating the ResourceClaim.  Exactly one of ResourceClaimName and ResourceClaimTemplateName must be set. | [optional] |
+
+## Example
+
+```ruby
+require 'kubevirt'
+
+instance = Kubevirt::K8sIoApiCoreV1PodResourceClaim.new(
+  name: null,
+  resource_claim_name: null,
+  resource_claim_template_name: null
+)
+```
+

data/docs/K8sIoApiCoreV1ResourceFieldSelector.md

@@ -5,7 +5,7 @@
 | Name | Type | Description | Notes |
 | ---- | ---- | ----------- | ----- |
 | **container_name** | **String** | Container name: required for volumes, optional for env vars | [optional] |
-| **divisor** | **String** | 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] |
+| **divisor** | **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] |
 | **resource** | **String** | Required: resource to select | [default to ''] |
 
 ## Example

data/docs/K8sIoApiCoreV1TopologySpreadConstraint.md

@@ -8,8 +8,8 @@
 | **match_label_keys** | **Array<String>** | MatchLabelKeys is a set of pod label keys to select the pods over which spreading will be calculated. The keys are used to lookup values from the incoming pod labels, those key-value labels are ANDed with labelSelector to select the group of existing pods over which spreading will be calculated for the incoming pod. The same key is forbidden to exist in both MatchLabelKeys and LabelSelector. MatchLabelKeys cannot be set when LabelSelector isn't set. Keys that don't exist in the incoming pod labels will be ignored. A null or empty list means only match against labelSelector.  This is a beta field and requires the MatchLabelKeysInPodTopologySpread feature gate to be enabled (enabled by default). | [optional] |
 | **max_skew** | **Integer** | MaxSkew describes the degree to which pods may be unevenly distributed. When `whenUnsatisfiable=DoNotSchedule`, it is the maximum permitted difference between the number of matching pods in the target topology and the global minimum. The global minimum is the minimum number of matching pods in an eligible domain or zero if the number of eligible domains is less than MinDomains. For example, in a 3-zone cluster, MaxSkew is set to 1, and pods with the same labelSelector spread as 2/2/1: In this case, the global minimum is 1. | zone1 | zone2 | zone3 | |  P P  |  P P  |   P   | - if MaxSkew is 1, incoming pod can only be scheduled to zone3 to become 2/2/2; scheduling it onto zone1(zone2) would make the ActualSkew(3-1) on zone1(zone2) violate MaxSkew(1). - if MaxSkew is 2, incoming pod can be scheduled onto any zone. When `whenUnsatisfiable=ScheduleAnyway`, it is used to give higher precedence to topologies that satisfy it. It's a required field. Default value is 1 and 0 is not allowed. | [default to 0] |
 | **min_domains** | **Integer** | MinDomains indicates a minimum number of eligible domains. When the number of eligible domains with matching topology keys is less than minDomains, Pod Topology Spread treats \"global minimum\" as 0, and then the calculation of Skew is performed. And when the number of eligible domains with matching topology keys equals or greater than minDomains, this value has no effect on scheduling. As a result, when the number of eligible domains is less than minDomains, scheduler won't schedule more than maxSkew Pods to those domains. If value is nil, the constraint behaves as if MinDomains is equal to 1. Valid values are integers greater than 0. When value is not nil, WhenUnsatisfiable must be DoNotSchedule.  For example, in a 3-zone cluster, MaxSkew is set to 2, MinDomains is set to 5 and pods with the same labelSelector spread as 2/2/2: | zone1 | zone2 | zone3 | |  P P  |  P P  |  P P  | The number of domains is less than 5(MinDomains), so \"global minimum\" is treated as 0. In this situation, new pod with the same labelSelector cannot be scheduled, because computed skew will be 3(3 - 0) if new Pod is scheduled to any of the three zones, it will violate MaxSkew. | [optional] |
-| **node_affinity_policy** | **String** | NodeAffinityPolicy indicates how we will treat Pod's nodeAffinity/nodeSelector when calculating pod topology spread skew. Options are: - Honor: only nodes matching nodeAffinity/nodeSelector are included in the calculations. - Ignore: nodeAffinity/nodeSelector are ignored. All nodes are included in the calculations.  If this value is nil, the behavior is equivalent to the Honor policy. This is a beta-level feature default enabled by the NodeInclusionPolicyInPodTopologySpread feature flag.  Possible enum values:  - `\"Honor\"` means use this scheduling directive when calculating pod topology spread skew.  - `\"Ignore\"` means ignore this scheduling directive when calculating pod topology spread skew. | [optional] |
-| **node_taints_policy** | **String** | NodeTaintsPolicy indicates how we will treat node taints when calculating pod topology spread skew. Options are: - Honor: nodes without taints, along with tainted nodes for which the incoming pod has a toleration, are included. - Ignore: node taints are ignored. All nodes are included.  If this value is nil, the behavior is equivalent to the Ignore policy. This is a beta-level feature default enabled by the NodeInclusionPolicyInPodTopologySpread feature flag.  Possible enum values:  - `\"Honor\"` means use this scheduling directive when calculating pod topology spread skew.  - `\"Ignore\"` means ignore this scheduling directive when calculating pod topology spread skew. | [optional] |
+| **node_affinity_policy** | **String** | NodeAffinityPolicy indicates how we will treat Pod's nodeAffinity/nodeSelector when calculating pod topology spread skew. Options are: - Honor: only nodes matching nodeAffinity/nodeSelector are included in the calculations. - Ignore: nodeAffinity/nodeSelector are ignored. All nodes are included in the calculations.  If this value is nil, the behavior is equivalent to the Honor policy.  Possible enum values:  - `\"Honor\"` means use this scheduling directive when calculating pod topology spread skew.  - `\"Ignore\"` means ignore this scheduling directive when calculating pod topology spread skew. | [optional] |
+| **node_taints_policy** | **String** | NodeTaintsPolicy indicates how we will treat node taints when calculating pod topology spread skew. Options are: - Honor: nodes without taints, along with tainted nodes for which the incoming pod has a toleration, are included. - Ignore: node taints are ignored. All nodes are included.  If this value is nil, the behavior is equivalent to the Ignore policy.  Possible enum values:  - `\"Honor\"` means use this scheduling directive when calculating pod topology spread skew.  - `\"Ignore\"` means ignore this scheduling directive when calculating pod topology spread skew. | [optional] |
 | **topology_key** | **String** | TopologyKey is the key of node labels. Nodes that have a label with this key and identical values are considered to be in the same topology. We consider each <key, value> as a \"bucket\", and try to put balanced number of pods into each bucket. We define a domain as a particular instance of a topology. Also, we define an eligible domain as a domain whose nodes meet the requirements of nodeAffinityPolicy and nodeTaintsPolicy. e.g. If TopologyKey is \"kubernetes.io/hostname\", each Node is a domain of that topology. And, if TopologyKey is \"topology.kubernetes.io/zone\", each zone is a domain of that topology. It's a required field. | [default to ''] |
 | **when_unsatisfiable** | **String** | WhenUnsatisfiable indicates how to deal with a pod if it doesn't satisfy the spread constraint. - DoNotSchedule (default) tells the scheduler not to schedule it. - ScheduleAnyway tells the scheduler to schedule the pod in any location,   but giving higher precedence to topologies that would help reduce the   skew. A constraint is considered \"Unsatisfiable\" for an incoming pod if and only if every possible node assignment for that pod would violate \"MaxSkew\" on some topology. For example, in a 3-zone cluster, MaxSkew is set to 1, and pods with the same labelSelector spread as 3/1/1: | zone1 | zone2 | zone3 | | P P P |   P   |   P   | If WhenUnsatisfiable is set to DoNotSchedule, incoming pod can only be scheduled to zone2(zone3) to become 3/2/1(3/1/2) as ActualSkew(2-1) on zone2(zone3) satisfies MaxSkew(1). In other words, the cluster can still be imbalanced, but scheduler won't make it *more* imbalanced. It's a required field.  Possible enum values:  - `\"DoNotSchedule\"` instructs the scheduler not to schedule the pod when constraints are not satisfied.  - `\"ScheduleAnyway\"` instructs the scheduler to schedule the pod even if constraints are not satisfied. | [default to ''] |
 

data/docs/K8sIoApiCoreV1VolumeResourceRequirements.md

@@ -4,8 +4,8 @@
 
 | Name | Type | Description | Notes |
 | ---- | ---- | ----------- | ----- |
-| **limits** | **Hash<String, String>** | Limits describes the maximum amount of compute resources allowed. More info: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/ | [optional] |
-| **requests** | **Hash<String, String>** | Requests describes the minimum amount of compute resources required. If Requests is omitted for a container, it defaults to Limits if that is explicitly specified, otherwise to an implementation-defined value. Requests cannot exceed Limits. More info: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/ | [optional] |
+| **limits** | **Hash<String, Object>** | Limits describes the maximum amount of compute resources allowed. More info: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/ | [optional] |
+| **requests** | **Hash<String, Object>** | Requests describes the minimum amount of compute resources required. If Requests is omitted for a container, it defaults to Limits if that is explicitly specified, otherwise to an implementation-defined value. Requests cannot exceed Limits. More info: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/ | [optional] |
 
 ## Example
 

data/docs/K8sIoApimachineryPkgApisMetaV1DeleteOptions.md

@@ -7,6 +7,7 @@
 | **api_version** | **String** | APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources | [optional] |
 | **dry_run** | **Array<String>** | When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed | [optional] |
 | **grace_period_seconds** | **Integer** | The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately. | [optional] |
+| **ignore_store_read_error_with_cluster_breaking_potential** | **Boolean** | if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it | [optional] |
 | **kind** | **String** | Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds | [optional] |
 | **orphan_dependents** | **Boolean** | Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both. | [optional] |
 | **preconditions** | [**K8sIoApimachineryPkgApisMetaV1Preconditions**](K8sIoApimachineryPkgApisMetaV1Preconditions.md) |  | [optional] |
@@ -21,6 +22,7 @@ instance = Kubevirt::K8sIoApimachineryPkgApisMetaV1DeleteOptions.new(
   api_version: null,
   dry_run: null,
   grace_period_seconds: null,
+  ignore_store_read_error_with_cluster_breaking_potential: null,
   kind: null,
   orphan_dependents: null,
   preconditions: null,

data/docs/V1ACPI.md

@@ -4,6 +4,7 @@
 
 | Name | Type | Description | Notes |
 | ---- | ---- | ----------- | ----- |
+| **msdm_name_ref** | **String** | Similar to SlicNameRef, another ACPI entry that is used in more recent Windows versions. The above points to the spec of MSDM too. | [optional] |
 | **slic_name_ref** | **String** | SlicNameRef should match the volume name of a secret object. The data in the secret should be a binary blob that follows the ACPI SLIC standard, see: https://learn.microsoft.com/en-us/previous-versions/windows/hardware/design/dn653305(v=vs.85) | [optional] |
 
 ## Example
@@ -12,6 +13,7 @@
 require 'kubevirt'
 
 instance = Kubevirt::V1ACPI.new(
+  msdm_name_ref: null,
   slic_name_ref: null
 )
 ```

data/docs/V1ArchConfiguration.md

@@ -8,6 +8,7 @@
 | **arm64** | [**V1ArchSpecificConfiguration**](V1ArchSpecificConfiguration.md) |  | [optional] |
 | **default_architecture** | **String** |  | [optional] |
 | **ppc64le** | [**V1ArchSpecificConfiguration**](V1ArchSpecificConfiguration.md) |  | [optional] |
+| **s390x** | [**V1ArchSpecificConfiguration**](V1ArchSpecificConfiguration.md) |  | [optional] |
 
 ## Example
 
@@ -18,7 +19,8 @@ instance = Kubevirt::V1ArchConfiguration.new(
   amd64: null,
   arm64: null,
   default_architecture: null,
-  ppc64le: null
+  ppc64le: null,
+  s390x: null
 )
 ```
 

data/docs/V1ChangedBlockTrackingSelectors.md

@@ -0,0 +1,20 @@
+# Kubevirt::V1ChangedBlockTrackingSelectors
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **namespace_label_selector** | [**K8sIoApimachineryPkgApisMetaV1LabelSelector**](K8sIoApimachineryPkgApisMetaV1LabelSelector.md) |  | [optional] |
+| **virtual_machine_label_selector** | [**K8sIoApimachineryPkgApisMetaV1LabelSelector**](K8sIoApimachineryPkgApisMetaV1LabelSelector.md) |  | [optional] |
+
+## Example
+
+```ruby
+require 'kubevirt'
+
+instance = Kubevirt::V1ChangedBlockTrackingSelectors.new(
+  namespace_label_selector: null,
+  virtual_machine_label_selector: null
+)
+```
+

data/docs/V1ChangedBlockTrackingStatus.md

@@ -0,0 +1,18 @@
+# Kubevirt::V1ChangedBlockTrackingStatus
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **state** | **String** | State represents the current CBT state | [default to ''] |
+
+## Example
+
+```ruby
+require 'kubevirt'
+
+instance = Kubevirt::V1ChangedBlockTrackingStatus.new(
+  state: null
+)
+```
+

data/docs/V1ControllerRevisionRef.md

@@ -0,0 +1,18 @@
+# Kubevirt::V1ControllerRevisionRef
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **name** | **String** | Name of the ControllerRevision | [optional] |
+
+## Example
+
+```ruby
+require 'kubevirt'
+
+instance = Kubevirt::V1ControllerRevisionRef.new(
+  name: null
+)
+```
+

data/docs/V1CustomBlockSize.md

@@ -4,8 +4,9 @@
 
 | Name | Type | Description | Notes |
 | ---- | ---- | ----------- | ----- |
-| **logical** | **Integer** |  | [default to 0] |
-| **physical** | **Integer** |  | [default to 0] |
+| **discard_granularity** | **Integer** |  | [optional] |
+| **logical** | **Integer** |  | [optional] |
+| **physical** | **Integer** |  | [optional] |
 
 ## Example
 
@@ -13,6 +14,7 @@
 require 'kubevirt'
 
 instance = Kubevirt::V1CustomBlockSize.new(
+  discard_granularity: null,
   logical: null,
   physical: null
 )

data/docs/V1DeveloperConfiguration.md

@@ -4,6 +4,7 @@
 
 | Name | Type | Description | Notes |
 | ---- | ---- | ----------- | ----- |
+| **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] |
 | **disk_verification** | [**V1DiskVerification**](V1DiskVerification.md) |  | [optional] |
 | **feature_gates** | **Array<String>** | FeatureGates is the list of experimental features to enable. Defaults to none | [optional] |
@@ -21,6 +22,7 @@
 require 'kubevirt'
 
 instance = Kubevirt::V1DeveloperConfiguration.new(
+  cluster_profiler: null,
   cpu_allocation_ratio: null,
   disk_verification: null,
   feature_gates: null,

data/docs/V1DeviceAttribute.md

@@ -0,0 +1,20 @@
+# Kubevirt::V1DeviceAttribute
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **m_dev_uuid** | **String** | MDevUUID is the mediated device uuid of the allocated device | [optional] |
+| **pci_address** | **String** | PCIAddress is the PCIe bus address of the allocated device | [optional] |
+
+## Example
+
+```ruby
+require 'kubevirt'
+
+instance = Kubevirt::V1DeviceAttribute.new(
+  m_dev_uuid: null,
+  pci_address: null
+)
+```
+

data/docs/V1DeviceResourceClaimStatus.md

@@ -0,0 +1,22 @@
+# Kubevirt::V1DeviceResourceClaimStatus
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **attributes** | [**V1DeviceAttribute**](V1DeviceAttribute.md) |  | [optional] |
+| **name** | **String** | Name is the name of actual device on the host provisioned by the driver as reflected in resourceclaim.status | [optional] |
+| **resource_claim_name** | **String** | ResourceClaimName is the name of the resource claims object used to provision this resource | [optional] |
+
+## Example
+
+```ruby
+require 'kubevirt'
+
+instance = Kubevirt::V1DeviceResourceClaimStatus.new(
+  attributes: null,
+  name: null,
+  resource_claim_name: null
+)
+```
+

data/docs/V1DeviceStatus.md

@@ -0,0 +1,20 @@
+# Kubevirt::V1DeviceStatus
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **gpu_statuses** | [**Array<V1DeviceStatusInfo>**](V1DeviceStatusInfo.md) | GPUStatuses reflects the state of GPUs requested in spec.domain.devices.gpus | [optional] |
+| **host_device_statuses** | [**Array<V1DeviceStatusInfo>**](V1DeviceStatusInfo.md) | HostDeviceStatuses reflects the state of GPUs requested in spec.domain.devices.hostDevices DRA | [optional] |
+
+## Example
+
+```ruby
+require 'kubevirt'
+
+instance = Kubevirt::V1DeviceStatus.new(
+  gpu_statuses: null,
+  host_device_statuses: null
+)
+```
+

data/docs/V1DeviceStatusInfo.md

@@ -0,0 +1,20 @@
+# Kubevirt::V1DeviceStatusInfo
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **device_resource_claim_status** | [**V1DeviceResourceClaimStatus**](V1DeviceResourceClaimStatus.md) |  | [optional] |
+| **name** | **String** | Name of the device as specified in spec.domain.devices.gpus.name or spec.domain.devices.hostDevices.name | [default to ''] |
+
+## Example
+
+```ruby
+require 'kubevirt'
+
+instance = Kubevirt::V1DeviceStatusInfo.new(
+  device_resource_claim_status: null,
+  name: null
+)
+```
+

data/docs/V1Devices.md

@@ -22,10 +22,12 @@
 | **interfaces** | [**Array<V1Interface>**](V1Interface.md) | Interfaces describe network interfaces which are added to the vmi. | [optional] |
 | **log_serial_console** | **Boolean** | Whether to log the auto-attached default serial console or not. Serial console logs will be collect to a file and then streamed from a named `guest-console-log`. Not relevant if autoattachSerialConsole is disabled. Defaults to cluster wide setting on VirtualMachineOptions. | [optional] |
 | **network_interface_multiqueue** | **Boolean** | If specified, virtual network interfaces configured with a virtio bus will also enable the vhost multiqueue feature for network devices. The number of queues created depends on additional factors of the VirtualMachineInstance, like the number of guest CPUs. | [optional] |
+| **panic_devices** | [**Array<V1PanicDevice>**](V1PanicDevice.md) | PanicDevices provides additional crash information when a guest crashes. | [optional] |
 | **rng** | **Object** | Rng represents the random device passed from host | [optional] |
 | **sound** | [**V1SoundDevice**](V1SoundDevice.md) |  | [optional] |
 | **tpm** | [**V1TPMDevice**](V1TPMDevice.md) |  | [optional] |
 | **use_virtio_transitional** | **Boolean** | Fall back to legacy virtio 0.9 support if virtio bus is selected on devices. This is helpful for old machines like CentOS6 or RHEL6 which do not understand virtio_non_transitional (virtio 1.0). | [optional] |
+| **video** | [**V1VideoDevice**](V1VideoDevice.md) |  | [optional] |
 | **watchdog** | [**V1Watchdog**](V1Watchdog.md) |  | [optional] |
 
 ## Example
@@ -52,10 +54,12 @@ instance = Kubevirt::V1Devices.new(
   interfaces: null,
   log_serial_console: null,
   network_interface_multiqueue: null,
+  panic_devices: null,
   rng: null,
   sound: null,
   tpm: null,
   use_virtio_transitional: null,
+  video: null,
   watchdog: null
 )
 ```

data/docs/V1Diag288Watchdog.md

@@ -0,0 +1,18 @@
+# Kubevirt::V1Diag288Watchdog
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **action** | **String** | The action to take. Valid values are poweroff, reset, shutdown. Defaults to reset. | [optional] |
+
+## Example
+
+```ruby
+require 'kubevirt'
+
+instance = Kubevirt::V1Diag288Watchdog.new(
+  action: null
+)
+```
+

data/docs/V1Disk.md

@@ -6,8 +6,9 @@
 | ---- | ---- | ----------- | ----- |
 | **block_size** | [**V1BlockSize**](V1BlockSize.md) |  | [optional] |
 | **boot_order** | **Integer** | BootOrder is an integer value > 0, used to determine ordering of boot devices. Lower values take precedence. Each disk or interface that has a boot order must have a unique value. Disks without a boot order are not tried if a disk with a boot order exists. | [optional] |
-| **cache** | **String** | Cache specifies which kvm disk cache mode should be used. Supported values are: CacheNone, CacheWriteThrough. | [optional] |
+| **cache** | **String** | Cache specifies which kvm disk cache mode should be used. Supported values are: none: Guest I/O not cached on the host, but may be kept in a disk cache. writethrough: Guest I/O cached on the host but written through to the physical medium. Slowest but with most guarantees. writeback: Guest I/O cached on the host. Defaults to none if the storage supports O_DIRECT, otherwise writethrough. | [optional] |
 | **cdrom** | [**V1CDRomTarget**](V1CDRomTarget.md) |  | [optional] |
+| **changed_block_tracking** | **Boolean** | ChangedBlockTracking indicates this disk should have CBT option Defaults to false. | [optional] |
 | **dedicated_io_thread** | **Boolean** | dedicatedIOThread indicates this disk should have an exclusive IO Thread. Enabling this implies useIOThreads = true. Defaults to false. | [optional] |
 | **disk** | [**V1DiskTarget**](V1DiskTarget.md) |  | [optional] |
 | **error_policy** | **String** | If specified, it can change the default error policy (stop) for the disk | [optional] |
@@ -28,6 +29,7 @@ instance = Kubevirt::V1Disk.new(
   boot_order: null,
   cache: null,
   cdrom: null,
+  changed_block_tracking: null,
   dedicated_io_thread: null,
   disk: null,
   error_policy: null,

data/docs/V1DiskIOThreads.md

@@ -0,0 +1,18 @@
+# Kubevirt::V1DiskIOThreads
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **supplemental_pool_thread_count** | **Integer** | SupplementalPoolThreadCount specifies how many iothreads are allocated for the supplementalPool policy. | [optional] |
+
+## Example
+
+```ruby
+require 'kubevirt'
+
+instance = Kubevirt::V1DiskIOThreads.new(
+  supplemental_pool_thread_count: null
+)
+```
+

data/docs/V1DiskVerification.md

@@ -4,7 +4,7 @@
 
 | Name | Type | Description | Notes |
 | ---- | ---- | ----------- | ----- |
-| **memory_limit** | **String** | 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. |  |
+| **memory_limit** | **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. |  |
 
 ## Example
 

data/docs/V1DomainSpec.md

@@ -10,7 +10,8 @@
 | **devices** | [**V1Devices**](V1Devices.md) |  |  |
 | **features** | [**V1Features**](V1Features.md) |  | [optional] |
 | **firmware** | [**V1Firmware**](V1Firmware.md) |  | [optional] |
-| **io_threads_policy** | **String** | Controls whether or not disks will share IOThreads. Omitting IOThreadsPolicy disables use of IOThreads. One of: shared, auto | [optional] |
+| **io_threads** | [**V1DiskIOThreads**](V1DiskIOThreads.md) |  | [optional] |
+| **io_threads_policy** | **String** | Controls whether or not disks will share IOThreads. Omitting IOThreadsPolicy disables use of IOThreads. One of: shared, auto, supplementalPool | [optional] |
 | **launch_security** | [**V1LaunchSecurity**](V1LaunchSecurity.md) |  | [optional] |
 | **machine** | [**V1Machine**](V1Machine.md) |  | [optional] |
 | **memory** | [**V1Memory**](V1Memory.md) |  | [optional] |
@@ -28,6 +29,7 @@ instance = Kubevirt::V1DomainSpec.new(
   devices: null,
   features: null,
   firmware: null,
+  io_threads: null,
   io_threads_policy: null,
   launch_security: null,
   machine: null,

data/docs/V1EmptyDiskSource.md

@@ -4,7 +4,7 @@
 
 | Name | Type | Description | Notes |
 | ---- | ---- | ----------- | ----- |
-| **capacity** | **String** | 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. |  |
+| **capacity** | **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. |  |
 
 ## Example
 

data/docs/V1EvacuateCancelOptions.md

@@ -0,0 +1,24 @@
+# Kubevirt::V1EvacuateCancelOptions
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **api_version** | **String** | APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources | [optional] |
+| **dry_run** | **Array<String>** | When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed | [optional] |
+| **evacuation_node_name** | **String** |  | [default to ''] |
+| **kind** | **String** | Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds | [optional] |
+
+## Example
+
+```ruby
+require 'kubevirt'
+
+instance = Kubevirt::V1EvacuateCancelOptions.new(
+  api_version: null,
+  dry_run: null,
+  evacuation_node_name: null,
+  kind: null
+)
+```
+

data/docs/V1GPU.md

@@ -4,8 +4,10 @@
 
 | Name | Type | Description | Notes |
 | ---- | ---- | ----------- | ----- |
-| **device_name** | **String** |  | [default to ''] |
+| **claim_name** | **String** | ClaimName needs to be provided from the list vmi.spec.resourceClaims[].name where this device is allocated | [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] |
 | **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] |
 
@@ -15,8 +17,10 @@
 require 'kubevirt'
 
 instance = Kubevirt::V1GPU.new(
+  claim_name: null,
   device_name: null,
   name: null,
+  request_name: null,
   tag: null,
   virtual_gpu_options: null
 )

data/docs/V1HostDevice.md

@@ -4,8 +4,10 @@
 
 | Name | Type | Description | Notes |
 | ---- | ---- | ----------- | ----- |
-| **device_name** | **String** | DeviceName is the resource name of the host device exposed by a device plugin | [default to ''] |
+| **claim_name** | **String** | ClaimName needs to be provided from the list vmi.spec.resourceClaims[].name where this device is allocated | [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] |
 | **tag** | **String** | If specified, the virtual network interface address and its tag will be provided to the guest via config drive | [optional] |
 
 ## Example
@@ -14,8 +16,10 @@
 require 'kubevirt'
 
 instance = Kubevirt::V1HostDevice.new(
+  claim_name: null,
   device_name: null,
   name: null,
+  request_name: null,
   tag: null
 )
 ```

data/docs/V1HostDisk.md

@@ -4,7 +4,7 @@
 
 | Name | Type | Description | Notes |
 | ---- | ---- | ----------- | ----- |
-| **capacity** | **String** | 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] |
+| **capacity** | **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] |
 | **path** | **String** | The path to HostDisk image located on the cluster | [default to ''] |
 | **shared** | **Boolean** | Shared indicate whether the path is shared between nodes | [optional] |
 | **type** | **String** | Contains information if disk.img exists or should be created allowed options are 'Disk' and 'DiskOrCreate' | [default to ''] |