InstanceGroupManagerAutoHealingPolicyResponse class
Constructors
-
InstanceGroupManagerAutoHealingPolicyResponse({required Input<InstanceGroupManagerAutoHealingPolicyAutoHealingTriggersResponse> autoHealingTriggers, required Input<String> healthCheck, required Input<int> initialDelaySec, required Input<FixedOrPercentResponse> maxUnavailable})
-
Creates a new InstanceGroupManagerAutoHealingPolicyResponse.
autoHealingTriggers Restricts what triggers autohealing.
healthCheck The URL for the health check that signals autohealing.
initialDelaySec The initial delay is the number of seconds that a new VM takes to initialize and run its startup script. During a VM's initial delay period, the MIG ignores unsuccessful health checks because the VM might be in the startup process. This prevents the MIG from prematurely recreating a VM. If the health check receives a healthy response during the initial delay, it indicates that the startup process is complete and the VM is ready. The value of initial delay must be between 0 and 3600 seconds. The default value is 0.
maxUnavailable Maximum number of instances that can be unavailable when autohealing. When 'percent' is used, the value is rounded if necessary. The instance is considered available if all of the following conditions are satisfied: 1. Instance's status is RUNNING. 2. Instance's currentAction is NONE (in particular its liveness health check result was observed to be HEALTHY at least once as it passed VERIFYING). 3. There is no outgoing action on an instance triggered by IGM. By default, number of concurrently autohealed instances is smaller than the managed instance group target size. However, if a zonal managed instance group has only one instance, or a regional managed instance group has only one instance per zone, autohealing will recreate these instances when they become unhealthy.
const
-
InstanceGroupManagerAutoHealingPolicyResponse.fromMap(Map<String, dynamic> map)
-
factory
Properties
-
autoHealingTriggers
→ Input<InstanceGroupManagerAutoHealingPolicyAutoHealingTriggersResponse>
-
Restricts what triggers autohealing.
final
-
hashCode
→ int
-
The hash code for this object.
no setterinherited
-
healthCheck
→ Input<String>
-
The URL for the health check that signals autohealing.
final
-
initialDelaySec
→ Input<int>
-
The initial delay is the number of seconds that a new VM takes to initialize and run its startup script. During a VM's initial delay period, the MIG ignores unsuccessful health checks because the VM might be in the startup process. This prevents the MIG from prematurely recreating a VM. If the health check receives a healthy response during the initial delay, it indicates that the startup process is complete and the VM is ready. The value of initial delay must be between 0 and 3600 seconds. The default value is 0.
final
-
maxUnavailable
→ Input<FixedOrPercentResponse>
-
Maximum number of instances that can be unavailable when autohealing. When 'percent' is used, the value is rounded if necessary. The instance is considered available if all of the following conditions are satisfied: 1. Instance's status is RUNNING. 2. Instance's currentAction is NONE (in particular its liveness health check result was observed to be HEALTHY at least once as it passed VERIFYING). 3. There is no outgoing action on an instance triggered by IGM. By default, number of concurrently autohealed instances is smaller than the managed instance group target size. However, if a zonal managed instance group has only one instance, or a regional managed instance group has only one instance per zone, autohealing will recreate these instances when they become unhealthy.
final
-
runtimeType
→ Type
-
A representation of the runtime type of the object.
no setterinherited
