| name |
Name of the resource.
The name must be 1-63 characters long, and comply with RFC1035. Must be a string 1-63 characters long and match the regular expression [a-z](?:[-a-z0-9]{0,61}[a-z0-9])? which means the first character must be a lowercase letter, and all following characters must be a dash, lowercase letter, or digit, except the last character, which cannot be a dash. Valid values satisfy the regex: [[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?]. (Required)
|
| autoscaling-policy subresource |
The configuration parameters for the autoscaling algorithm.
You can define one or more of the policies for an autoscaler:
cpu-utilizationcustom-metric-utilizationsload-balancing-utilization
If none of these are specified, the default will be to autoscale based on cpu-utilization to 0.6 or 60%. (Required)
- cool-down-period-sec
The number of seconds that the autoscaler should wait before it starts collecting information from a new instance.
This prevents the autoscaler from collecting information when the instance is initializing, during which the collected usage would not be reliable. The default time autoscaler waits is 60 seconds. Virtual machine initialization times might vary because of numerous factors. We recommend that you test how long an instance may take to initialize. To do this, create an instance and time the startup process.
- cpu-utilization subresource
Defines the CPU utilization policy that allows the autoscaler to scale based on the average CPU utilization of a managed instance group.
- utilization-target
The target CPU utilization that the autoscaler should maintain.
Must be a float value in the range between 0 and 1. If not specified, the default is 0.6. If the CPU level is below the target utilization, the autoscaler scales down the number of instances until it reaches the minimum number of instances you specified or until the average CPU of your instances reaches the target utilization. If the average CPU is above the target utilization, the autoscaler scales up until it reaches the maximum number of instances you specified or until the average utilization reaches the target utilization. Valid values are between 0 to 1. (Required)
- custom-metric-utilization list subresource
Configuration parameters of autoscaling based on a custom metric.
- metric
The identifier (type) of the Stackdriver Monitoring metric.
The metric cannot have negative values. The metric must have a value type of INT64 or DOUBLE. (Required)
- utilization-target
The target value of the metric that autoscaler should maintain.
A utilization metric scales number of virtual machines handling requests to increase or decrease proportionally to the metric. For example, a good metric to use as a utilization_target is compute.googleapis.com/instance/network/received_bytes_count. The autoscaler will work to keep this value constant for each of the instances. Minimum allowed value is 0. (Required)
- utilization-target-type
Defines how target utilization value is expressed for a Stackdriver Monitoring metric.
Either
GAUGEDELTA_PER_SECONDDELTA_PER_MINUTE Valid values are DELTA_PER_MINUTE, DELTA_PER_SECOND or GAUGE.
- load-balancing-utilization subresource
Configuration parameters of autoscaling based on load balancer.
- utilization-target
Fraction of backend capacity utilization (set in HTTP(S) load balancing configuration) that autoscaler should maintain.
Must be a positive float value. If not defined, the default is 0.8. Valid values are between 0 to 1. (Required)
- max-num-replicas
The maximum number of instances that the autoscaler can scale up to.
The maximum number of replicas should not be lower than minimal number of replicas. (Required)
- min-num-replicas
The minimum number of replicas that the autoscaler can scale down to.
If not provided, autoscaler will choose a default value depending on maximum number of instances allowed. Minimum allowed value is 0.
- mode
- Operating mode for this policy. Valid values are
OFF, ON or ONLY_UP.
|