Package io.kubernetes.client.openapi.models

Class V2HPAScalingRules

java.lang.Object
io.kubernetes.client.openapi.models.V2HPAScalingRules
@Generated(value="org.openapitools.codegen.languages.JavaClientCodegen", date="2025-05-22T21:20:49.874193Z[Etc/UTC]") public class V2HPAScalingRules extends Object
HPAScalingRules configures the scaling behavior for one direction via scaling Policy Rules and a configurable metric tolerance. Scaling Policy Rules are applied after calculating DesiredReplicas from metrics for the HPA. They can limit the scaling velocity by specifying scaling policies. They can prevent flapping by specifying the stabilization window, so that the number of replicas is not set instantly, instead, the safest value from the stabilization window is chosen. The tolerance is applied to the metric values and prevents scaling too eagerly for small metric variations. (Note that setting a tolerance requires enabling the alpha HPAConfigurableTolerance feature gate.)

  • Field Details

  • Constructor Details

    • V2HPAScalingRules

      public V2HPAScalingRules()

  • Method Details

    • policies

      public V2HPAScalingRules policies(List<V2HPAScalingPolicy> policies)

    • addPoliciesItem

      public V2HPAScalingRules addPoliciesItem(V2HPAScalingPolicy policiesItem)

    • getPolicies

      @Nullable public List<V2HPAScalingPolicy> getPolicies()
      policies is a list of potential scaling polices which can be used during scaling. If not set, use the default values: - For scale up: allow doubling the number of pods, or an absolute change of 4 pods in a 15s window. - For scale down: allow all pods to be removed in a 15s window.
      Returns:
      policies

    • setPolicies

      public void setPolicies(List<V2HPAScalingPolicy> policies)

    • selectPolicy

      public V2HPAScalingRules selectPolicy(String selectPolicy)

    • getSelectPolicy

      @Nullable public String getSelectPolicy()
      selectPolicy is used to specify which policy should be used. If not set, the default value Max is used.
      Returns:
      selectPolicy

    • setSelectPolicy

      public void setSelectPolicy(String selectPolicy)

    • stabilizationWindowSeconds

      public V2HPAScalingRules stabilizationWindowSeconds(Integer stabilizationWindowSeconds)

    • getStabilizationWindowSeconds

      @Nullable public Integer getStabilizationWindowSeconds()
      stabilizationWindowSeconds is the number of seconds for which past recommendations should be considered while scaling up or scaling down. StabilizationWindowSeconds must be greater than or equal to zero and less than or equal to 3600 (one hour). If not set, use the default values: - For scale up: 0 (i.e. no stabilization is done). - For scale down: 300 (i.e. the stabilization window is 300 seconds long).
      Returns:
      stabilizationWindowSeconds

    • setStabilizationWindowSeconds

      public void setStabilizationWindowSeconds(Integer stabilizationWindowSeconds)

    • tolerance

      public V2HPAScalingRules tolerance(Quantity tolerance)

    • getTolerance

      @Nullable public Quantity getTolerance()
      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:
      tolerance

    • setTolerance

      public void setTolerance(Quantity tolerance)

    • 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