1apiVersion: compute.gcp.m.upbound.io/v1beta1
2kind: RegionAutoscaler
RegionAutoscalerSpec defines the desired state of RegionAutoscaler
(No description available)
The configuration parameters for the autoscaling algorithm. You can define one or more of the policies for an autoscaler: cpuUtilization, customMetricUtilizations, and loadBalancingUtilization. If none of these are specified, the default will be to autoscale based on cpuUtilization to 0.6 or 60%. Structure is documented below.
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.
Configuration parameters of autoscaling based on a load balancer. Structure is documented below.
Configuration parameters of autoscaling based on a custom metric. Structure is documented below.
Defines scale in controls to reduce the risk of response latency and outages due to abrupt scale-in events Structure is documented below.
Scaling schedules defined for an autoscaler. Multiple schedules can be set on an autoscaler and they can overlap. Structure is documented below.
Reference to a RegionInstanceGroupManager in compute to populate target.
Policies for referencing.
Selector for a RegionInstanceGroupManager in compute to populate target.
Policies for selection.
THIS IS A BETA FIELD. It will be honored unless the Management Policies feature flag is disabled. InitProvider holds the same fields as ForProvider, with the exception of Identifier and other resource reference fields. The fields that are in InitProvider are merged into ForProvider when the resource is created. The same fields are also added to the terraform ignore_changes hook, to avoid updating them after creation. This is useful for fields that are required on creation, but we do not desire to update them after creation, for example because of an external controller is managing them, like an autoscaler.
The configuration parameters for the autoscaling algorithm. You can define one or more of the policies for an autoscaler: cpuUtilization, customMetricUtilizations, and loadBalancingUtilization. If none of these are specified, the default will be to autoscale based on cpuUtilization to 0.6 or 60%. Structure is documented below.
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.
Configuration parameters of autoscaling based on a load balancer. Structure is documented below.
Configuration parameters of autoscaling based on a custom metric. Structure is documented below.
Defines scale in controls to reduce the risk of response latency and outages due to abrupt scale-in events Structure is documented below.
Scaling schedules defined for an autoscaler. Multiple schedules can be set on an autoscaler and they can overlap. Structure is documented below.
Reference to a RegionInstanceGroupManager in compute to populate target.
Policies for referencing.
Selector for a RegionInstanceGroupManager in compute to populate target.
Policies for selection.
THIS IS A BETA FIELD. It is on by default but can be opted out through a Crossplane feature flag. ManagementPolicies specify the array of actions Crossplane is allowed to take on the managed and external resources. See the design doc for more information: https://github.com/crossplane/crossplane/blob/499895a25d1a1a0ba1604944ef98ac7a1a71f197/design/design-doc-observe-only-resources.md?plain=1#L223 and this one: https://github.com/crossplane/crossplane/blob/444267e84783136daa93568b364a5f01228cacbe/design/one-pager-ignore-changes.md
WriteConnectionSecretToReference specifies the namespace and name of a Secret to which any connection details for this managed resource should be written. Connection details frequently include the endpoint, username, and password required to connect to the managed resource.
RegionAutoscalerStatus defines the observed state of RegionAutoscaler.
(No description available)
The configuration parameters for the autoscaling algorithm. You can define one or more of the policies for an autoscaler: cpuUtilization, customMetricUtilizations, and loadBalancingUtilization. If none of these are specified, the default will be to autoscale based on cpuUtilization to 0.6 or 60%. Structure is documented below.
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.
Configuration parameters of autoscaling based on a load balancer. Structure is documented below.
Configuration parameters of autoscaling based on a custom metric. Structure is documented below.
Defines scale in controls to reduce the risk of response latency and outages due to abrupt scale-in events Structure is documented below.
Scaling schedules defined for an autoscaler. Multiple schedules can be set on an autoscaler and they can overlap. Structure is documented below.
Conditions of the resource.