You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+28-1
Original file line number
Diff line number
Diff line change
@@ -148,7 +148,34 @@ Once you have created the parameter, you must remove the variable `runners_token
148
148
149
149
Finally, the runner still supports the manual runner creation. No changes are required. Please keep in mind that this setup will be removed in future releases.
150
150
151
-
### Auto Scaling Group Instance Termination
151
+
### Auto Scaling Group
152
+
153
+
#### Scheduled scaling
154
+
155
+
When `enable_schedule=true`, the `schedule_config` variable can be used to scale the Auto Scaling group.
156
+
157
+
Scaling may be defined with one `scale_out` scheduled action and/or one `scale_in` scheduled action.
158
+
159
+
For example:
160
+
```hcl
161
+
module "runner" {
162
+
...
163
+
enable_schedule = true
164
+
schedule_config = {
165
+
# Configure optional scale_out scheduled action
166
+
scale_out_recurrence = "0 8 * * 1-5"
167
+
scale_out_count = 1 # Default for min_size, desired_capacity and max_size
description="Map containing the configuration of the ASG scale-in and scale-up for the runner instance. Will only be used if enable_schedule is set to true. "
637
637
type=map(any)
638
638
default={
639
-
scale_in_recurrence ="0 18 * * 1-5"
640
-
scale_in_count =0
639
+
# Configure optional scale_out scheduled action
641
640
scale_out_recurrence ="0 8 * * 1-5"
642
-
scale_out_count =1
641
+
scale_out_count =1# Default for min_size, desired_capacity and max_size
0 commit comments