Package com.pulumi.gcp.compute.outputs
Class RegionAutoscalerAutoscalingPolicy
- java.lang.Object
-
- com.pulumi.gcp.compute.outputs.RegionAutoscalerAutoscalingPolicy
-
public final class RegionAutoscalerAutoscalingPolicy extends java.lang.Object
-
-
Nested Class Summary
Nested Classes Modifier and Type Class Description static class
RegionAutoscalerAutoscalingPolicy.Builder
-
Method Summary
All Methods Static Methods Instance Methods Concrete Methods Modifier and Type Method Description static RegionAutoscalerAutoscalingPolicy.Builder
builder()
static RegionAutoscalerAutoscalingPolicy.Builder
builder(RegionAutoscalerAutoscalingPolicy defaults)
java.util.Optional<java.lang.Integer>
cooldownPeriod()
java.util.Optional<RegionAutoscalerAutoscalingPolicyCpuUtilization>
cpuUtilization()
java.util.Optional<RegionAutoscalerAutoscalingPolicyLoadBalancingUtilization>
loadBalancingUtilization()
java.lang.Integer
maxReplicas()
java.util.List<RegionAutoscalerAutoscalingPolicyMetric>
metrics()
java.lang.Integer
minReplicas()
java.util.Optional<java.lang.String>
mode()
java.util.Optional<RegionAutoscalerAutoscalingPolicyScaleDownControl>
scaleDownControl()
java.util.Optional<RegionAutoscalerAutoscalingPolicyScaleInControl>
scaleInControl()
java.util.List<RegionAutoscalerAutoscalingPolicyScalingSchedule>
scalingSchedules()
-
-
-
Method Detail
-
cooldownPeriod
public java.util.Optional<java.lang.Integer> cooldownPeriod()
- Returns:
- 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.
-
cpuUtilization
public java.util.Optional<RegionAutoscalerAutoscalingPolicyCpuUtilization> cpuUtilization()
- Returns:
- Defines the CPU utilization policy that allows the autoscaler to scale based on the average CPU utilization of a managed instance group. Structure is documented below.
-
loadBalancingUtilization
public java.util.Optional<RegionAutoscalerAutoscalingPolicyLoadBalancingUtilization> loadBalancingUtilization()
- Returns:
- Configuration parameters of autoscaling based on a load balancer. Structure is documented below.
-
maxReplicas
public java.lang.Integer maxReplicas()
- Returns:
- The maximum number of instances that the autoscaler can scale up to. This is required when creating or updating an autoscaler. The maximum number of replicas should not be lower than minimal number of replicas.
-
metrics
public java.util.List<RegionAutoscalerAutoscalingPolicyMetric> metrics()
- Returns:
- Configuration parameters of autoscaling based on a custom metric. Structure is documented below.
-
minReplicas
public java.lang.Integer minReplicas()
- Returns:
- The minimum number of replicas that the autoscaler can scale down to. This cannot be less than 0. If not provided, autoscaler will choose a default value depending on maximum number of instances allowed.
-
mode
public java.util.Optional<java.lang.String> mode()
- Returns:
- Defines operating mode for this policy. Default value is `ON`. Possible values are: `OFF`, `ONLY_UP`, `ON`.
-
scaleDownControl
public java.util.Optional<RegionAutoscalerAutoscalingPolicyScaleDownControl> scaleDownControl()
- Returns:
- Defines scale down controls to reduce the risk of response latency and outages due to abrupt scale-in events Structure is documented below.
-
scaleInControl
public java.util.Optional<RegionAutoscalerAutoscalingPolicyScaleInControl> scaleInControl()
- Returns:
- Defines scale in controls to reduce the risk of response latency and outages due to abrupt scale-in events Structure is documented below.
-
scalingSchedules
public java.util.List<RegionAutoscalerAutoscalingPolicyScalingSchedule> scalingSchedules()
- Returns:
- Scaling schedules defined for an autoscaler. Multiple schedules can be set on an autoscaler and they can overlap. Structure is documented below.
-
builder
public static RegionAutoscalerAutoscalingPolicy.Builder builder()
-
builder
public static RegionAutoscalerAutoscalingPolicy.Builder builder(RegionAutoscalerAutoscalingPolicy defaults)
-
-