Class V2MetricTarget
java.lang.Object
io.micronaut.kubernetes.client.openapi.model.V2MetricTarget
@Generated("io.micronaut.openapi.generator.JavaMicronautClientCodegen")
public class V2MetricTarget
extends Object
MetricTarget defines the target value, average value, or average utilization of a specific metric
-
Field Summary
-
Constructor Summary
-
Method Summary
Modifier and TypeMethodDescriptionaverageUtilization
(Integer averageUtilization) Set averageUtilization in a chainable fashion.averageValue
(String averageValue) Set averageValue in a chainable fashion.boolean
averageUtilization is the target value of the average of the resource metric across all relevant pods, represented as a percentage of the requested value of the resource for the pods.Quantity is a fixed-point representation of a number.getType()
type represents whether the metric type is Utilization, Value, or AverageValuegetValue()
Quantity is a fixed-point representation of a number.int
hashCode()
void
setAverageUtilization
(Integer averageUtilization) Set the averageUtilization property valuevoid
setAverageValue
(String averageValue) Set the averageValue property valuevoid
Set the type property valuevoid
Set the value property valuetoString()
Set type in a chainable fashion.Set value in a chainable fashion.
-
Field Details
-
JSON_PROPERTY_AVERAGE_UTILIZATION
- See Also:
-
JSON_PROPERTY_AVERAGE_VALUE
- See Also:
-
JSON_PROPERTY_TYPE
- See Also:
-
JSON_PROPERTY_VALUE
- See Also:
-
-
Constructor Details
-
V2MetricTarget
-
-
Method Details
-
getAverageUtilization
averageUtilization is the target value of the average of the resource metric across all relevant pods, represented as a percentage of the requested value of the resource for the pods. Currently only valid for Resource metric source type- Returns:
- the averageUtilization property value
-
setAverageUtilization
Set the averageUtilization property value -
averageUtilization
Set averageUtilization in a chainable fashion.- Returns:
- The same instance of V2MetricTarget for chaining.
-
getAverageValue
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:
- the averageValue property value
-
setAverageValue
Set the averageValue property value -
averageValue
Set averageValue in a chainable fashion.- Returns:
- The same instance of V2MetricTarget for chaining.
-
getType
type represents whether the metric type is Utilization, Value, or AverageValue- Returns:
- the type property value
-
setType
Set the type property value -
type
Set type in a chainable fashion.- Returns:
- The same instance of V2MetricTarget for chaining.
-
getValue
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:
- the value property value
-
setValue
Set the value property value -
value
Set value in a chainable fashion.- Returns:
- The same instance of V2MetricTarget for chaining.
-
equals
-
hashCode
public int hashCode() -
toString
-