Package net.stickycode.kuuty.model.v18
Class IoK8sApiAutoscalingV2beta1ExternalMetricSource
- java.lang.Object
-
- net.stickycode.kuuty.model.v18.IoK8sApiAutoscalingV2beta1ExternalMetricSource
-
@Generated(value="org.openapitools.codegen.languages.JavaClientCodegen", date="2020-11-26T11:01:11.402583+13:00[Pacific/Auckland]") public class IoK8sApiAutoscalingV2beta1ExternalMetricSource extends Object
ExternalMetricSource indicates how to scale on a metric not associated with any Kubernetes object (for example length of queue in cloud messaging service, or QPS from loadbalancer running outside of cluster). Exactly one \"target\" type should be set.
-
-
Field Summary
Fields Modifier and Type Field Description static StringJSON_PROPERTY_METRIC_NAMEstatic StringJSON_PROPERTY_METRIC_SELECTORstatic StringJSON_PROPERTY_TARGET_AVERAGE_VALUEstatic StringJSON_PROPERTY_TARGET_VALUE
-
Constructor Summary
Constructors Constructor Description IoK8sApiAutoscalingV2beta1ExternalMetricSource()
-
Method Summary
-
-
-
Field Detail
-
JSON_PROPERTY_METRIC_NAME
public static final String JSON_PROPERTY_METRIC_NAME
- See Also:
- Constant Field Values
-
JSON_PROPERTY_METRIC_SELECTOR
public static final String JSON_PROPERTY_METRIC_SELECTOR
- See Also:
- Constant Field Values
-
JSON_PROPERTY_TARGET_AVERAGE_VALUE
public static final String JSON_PROPERTY_TARGET_AVERAGE_VALUE
- See Also:
- Constant Field Values
-
JSON_PROPERTY_TARGET_VALUE
public static final String JSON_PROPERTY_TARGET_VALUE
- See Also:
- Constant Field Values
-
-
Method Detail
-
metricName
public IoK8sApiAutoscalingV2beta1ExternalMetricSource metricName(String metricName)
-
getMetricName
public String getMetricName()
metricName is the name of the metric in question.- Returns:
- metricName
-
setMetricName
public void setMetricName(String metricName)
-
metricSelector
public IoK8sApiAutoscalingV2beta1ExternalMetricSource metricSelector(IoK8sApimachineryPkgApisMetaV1LabelSelector metricSelector)
-
getMetricSelector
@Nullable public IoK8sApimachineryPkgApisMetaV1LabelSelector getMetricSelector()
Get metricSelector- Returns:
- metricSelector
-
setMetricSelector
public void setMetricSelector(IoK8sApimachineryPkgApisMetaV1LabelSelector metricSelector)
-
targetAverageValue
public IoK8sApiAutoscalingV2beta1ExternalMetricSource targetAverageValue(String targetAverageValue)
-
getTargetAverageValue
@Nullable public String getTargetAverageValue()
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: a. No precision is lost b. No fractional digits will be emitted c. 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:
- targetAverageValue
-
setTargetAverageValue
public void setTargetAverageValue(String targetAverageValue)
-
targetValue
public IoK8sApiAutoscalingV2beta1ExternalMetricSource targetValue(String targetValue)
-
getTargetValue
@Nullable public String getTargetValue()
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: a. No precision is lost b. No fractional digits will be emitted c. 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:
- targetValue
-
setTargetValue
public void setTargetValue(String targetValue)
-
-