Package io.kubernetes.client.openapi.models

Class V1beta1CapacityRequestPolicy

java.lang.Object
io.kubernetes.client.openapi.models.V1beta1CapacityRequestPolicy
@Generated(value="org.openapitools.codegen.languages.JavaClientCodegen", date="2025-09-12T23:11:52.603861Z[Etc/UTC]") public class V1beta1CapacityRequestPolicy extends Object
CapacityRequestPolicy defines how requests consume device capacity. Must not set more than one ValidRequestValues.

  • Field Details

  • Constructor Details

    • V1beta1CapacityRequestPolicy

      public V1beta1CapacityRequestPolicy()

  • Method Details

    • _default

      public V1beta1CapacityRequestPolicy _default(Quantity _default)

    • getDefault

      @Nullable public Quantity getDefault()
      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:
      _default

    • setDefault

      public void setDefault(Quantity _default)

    • validRange

      public V1beta1CapacityRequestPolicy validRange(V1beta1CapacityRequestPolicyRange validRange)

    • getValidRange

      @Nullable public V1beta1CapacityRequestPolicyRange getValidRange()
      Get validRange
      Returns:
      validRange

    • setValidRange

      public void setValidRange(V1beta1CapacityRequestPolicyRange validRange)

    • validValues

      public V1beta1CapacityRequestPolicy validValues(List<Quantity> validValues)

    • addValidValuesItem

      public V1beta1CapacityRequestPolicy addValidValuesItem(Quantity validValuesItem)

    • getValidValues

      @Nullable public List<Quantity> getValidValues()
      ValidValues defines a set of acceptable quantity values in consuming requests. Must not contain more than 10 entries. Must be sorted in ascending order. If this field is set, Default must be defined and it must be included in ValidValues list. If the requested amount does not match any valid value but smaller than some valid values, the scheduler calculates the smallest valid value that is greater than or equal to the request. That is: min(ceil(requestedValue) ∈ validValues), where requestedValue ≤ max(validValues). If the requested amount exceeds all valid values, the request violates the policy, and this device cannot be allocated.
      Returns:
      validValues

    • setValidValues

      public void setValidValues(List<Quantity> validValues)

    • equals

      public boolean equals(Object o)
      Overrides:
      equals in class Object

    • hashCode

      public int hashCode()
      Overrides:
      hashCode in class Object

    • toString

      public String toString()
      Overrides:
      toString in class Object