Missed Team ’24? Catch up on announcements here.

×
Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Runner Autoscaler couldn't reload automatically once runners-autoscaler-config ConfigMap get updated

Aaron.Luo May 15, 2022

Hi team,

While I was testing Runner Autoscaler, I found Runner Autoscaler couldn't reload automatically once runners-autoscaler-config ConfigMap got updated. Could you advise how could we make it auto reload the configuration automatically? Thanks.

Kind regards,

Aaron

1 comment

Comment

Log in or Sign up to comment
Oleksandr Kyrdan
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
December 22, 2022

Hi @Aaron.Luo 

Thank you for your question!

Now the latest version of the Runner Autoscaler supports the auto-reloading of the runners-autoscaler-config.

Runner Autoscaler re-reads config each tick according to the constant value runner_api_polling_interval provided in the config/runners-autoscaler-cm.yaml file.

Default value of runner_api_polling_interval is 600 sec but you could modify it according to your needs.

config/runners-autoscaler-cm.yaml

groups:
  - name: "Runner repository group"       # Name of the Runner displayed in the Bitbucket Runner UI.
    workspace: "myworkspace"              # Name of the workspace the Runner is added to. 
    repository: "my-awesome-repository"   # Name of the repository the Runner is added to. Optional: Provide the repository name if you want the Runner to be added at the repository level.
    labels:
      - "demo1"                           # Labels for the Runner.
      - "test2"                           # Labels for the Runner.
    namespace: "runner-group-1"           # Kubernetes namespace to set up the Runner on.
    strategy: "percentageRunnersIdle"     # Type of the strategy workflow.
    parameters:
      min: 1  # recommended minimum 1 must be in UI to prevent pipeline fails, when new build is starting
      max: 10  # maximum allowed runners count
      scaleUpThreshold: 0.8  # The percentage of busy runners at which the number of desired runners are re-evaluated to scale up
      scaleDownThreshold: 0.2  # The percentage of busy runners at which the number of desired runners are re-evaluated to scale up
      scaleUpMultiplier: 1.5  #  scaleUpMultiplier > 1  speed to scale up
      scaleDownMultiplier: 0.5  #  0 < scaleDownMultiplier < 1  speed to scale down

constants:  # autoscaler parameters available for tuning
  default_sleep_time_runner_setup: 5  # seconds. Time between runners creation.
  default_sleep_time_runner_delete: 5  # seconds. Time between runners deletion.
  runner_api_polling_interval: 600  # seconds. Time between requests to Bitbucket API.
  runner_cool_down_period: 300  # seconds. Time reserved for runner to set up.

 

Best regards,
Oleksandr Kyrdan

TAGS
AUG Leaders

Atlassian Community Events