Class V1NodeAllocatableResourceMapping
java.lang.Object
io.kubernetes.client.openapi.models.V1NodeAllocatableResourceMapping
@Generated(value="org.openapitools.codegen.languages.JavaClientCodegen",
date="2026-06-26T22:35:15.319369Z[Etc/UTC]",
comments="Generator version: 7.18.0")
public class V1NodeAllocatableResourceMapping
extends Object
NodeAllocatableResourceMapping defines the translation between the DRA device/capacity units requested to the corresponding quantity of the node allocatable resource.
-
Nested Class Summary
Nested ClassesModifier and TypeClassDescriptionstatic class -
Field Summary
Fields -
Constructor Summary
Constructors -
Method Summary
Modifier and TypeMethodDescriptionallocationMultiplier(Quantity allocationMultiplier) capacityKey(String capacityKey) booleanCreate an instance of V1NodeAllocatableResourceMapping given an JSON stringQuantity is a fixed-point representation of a number.CapacityKey references a capacity name defined as a key in the `spec.devices[*].capacity` map.inthashCode()voidsetAllocationMultiplier(Quantity allocationMultiplier) voidsetCapacityKey(String capacityKey) toJson()Convert an instance of V1NodeAllocatableResourceMapping to an JSON stringtoString()static voidvalidateJsonElement(com.google.gson.JsonElement jsonElement) Validates the JSON Element and throws an exception if issues found
-
Field Details
-
SERIALIZED_NAME_ALLOCATION_MULTIPLIER
- See Also:
-
SERIALIZED_NAME_CAPACITY_KEY
- See Also:
-
openapiFields
-
openapiRequiredFields
-
-
Constructor Details
-
V1NodeAllocatableResourceMapping
public V1NodeAllocatableResourceMapping()
-
-
Method Details
-
allocationMultiplier
public V1NodeAllocatableResourceMapping allocationMultiplier(@Nullable Quantity allocationMultiplier) -
getAllocationMultiplier
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.- Returns:
- allocationMultiplier
-
setAllocationMultiplier
-
capacityKey
-
getCapacityKey
CapacityKey references a capacity name defined as a key in the `spec.devices[*].capacity` map. When this field is set, the value associated with this key in the `status.allocation.devices.results[*].consumedCapacity` map (for a specific claim allocation) determines the base quantity for the node allocatable resource. If `allocationMultiplier` is also set, it is multiplied with the base quantity. For example, if `spec.devices[*].capacity` has an entry \"dra.example.com/memory\": \"128Gi\", and this field is set to \"dra.example.com/memory\", then for a claim allocation that consumes { \"dra.example.com/memory\": \"4Gi\" } the base quantity for the node allocatable resource mapping will be \"4Gi\", and `allocationMultiplier` should be omitted or set to \"1\".- Returns:
- capacityKey
-
setCapacityKey
-
equals
-
hashCode
public int hashCode() -
toString
-
validateJsonElement
Validates the JSON Element and throws an exception if issues found- Parameters:
jsonElement- JSON Element- Throws:
IOException- if the JSON Element is invalid with respect to V1NodeAllocatableResourceMapping
-
fromJson
Create an instance of V1NodeAllocatableResourceMapping given an JSON string- Parameters:
jsonString- JSON string- Returns:
- An instance of V1NodeAllocatableResourceMapping
- Throws:
IOException- if the JSON string is invalid with respect to V1NodeAllocatableResourceMapping
-
toJson
Convert an instance of V1NodeAllocatableResourceMapping to an JSON string- Returns:
- JSON string
-