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
feat(pool): Allow to optionally include busy runners into the pool
'pool_config' is useful when one wants to ensure that a certain number
of runners is running within given time periods.
However, when 'pool_config' is used in a combination with persistent runners,
the pool lambda tends to spin up new runner instance when it sees that some
existing runners are online, but busy.
As a result, with frequent pool lambda checks, the total size of the runners
pool tends to grow more than desired (without respecting
'runners_maximum_count', which is only considered by the 'scale_up' lambda).
These changes introduce a new 'pool_include_busy_runners' module variable
to make it possbile to include all online runners (both idle and busy)
into the pool, so that the pool's lambda only tops up the pool if not
enough runners are online.
Copy file name to clipboardExpand all lines: modules/runners/variables.tf
+6Lines changed: 6 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -572,6 +572,12 @@ variable "pool_config" {
572
572
default=[]
573
573
}
574
574
575
+
variable"pool_include_busy_runners" {
576
+
description="Include busy runners in the pool calculation. By default busy runners are not included in the pool."
577
+
type=bool
578
+
default=false
579
+
}
580
+
575
581
variable"disable_runner_autoupdate" {
576
582
description="Disable the auto update of the github runner agent. Be aware there is a grace period of 30 days, see also the [GitHub article](https://github.blog/changelog/2022-02-01-github-actions-self-hosted-runners-can-now-disable-automatic-updates/)"
0 commit comments