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: add update_interval and update_interval_when_expecting (#1173)
## Description
It seems that the default values set by GitLab are not perfect. I often
saw rate limiting on the AWS API for autoscaling. Making these variables
configurable ensures to stay below the limits. These variable have the
same defaults as documented by GitLab:
https://docs.gitlab.com/runner/configuration/advanced-configuration.html#the-runnersautoscaler-section
The best values depend on how many Runners you have deployed.
## Verification
None
connector_config_user = User to connect to worker machine
608
608
key_pair_name = The name of the key pair used by the Runner to connect to the docker-machine Runner Workers. This variable is only supported when `enables` is set to `true`.
609
609
max_use_count = Max job number that can run on a worker
610
+
update_interval = The interval to check with the fleeting plugin for instance updates.
611
+
update_interval_when_expecting = The interval to check with the fleeting plugin for instance updates when expecting a state change.
0 commit comments