Skip to content

Adjust autoscaler policy on config reloading

Arran Walker requested to merge 29314-detect-config-changes into main

What does this MR do?

Refreshes the autoscaler policy when the config is reloaded.

Why was this MR needed?

So that scaling modifications can be made without restarting Runner.

What's the best way to test this MR?

Adjust the policy when Runner is running. Observe instances go up and down.

[[runners]]
  name = "linuxrunner"
  url = "https://gitlab.com"
  token = "<token>"
  executor = "docker-autoscaler"
  [runners.docker]
    image = "busybox:latest"
    privileged = true
  [runners.autoscaler]
    capacity_per_instance = 1
    max_use_count = 1
    max_instances = 5
    plugin = "googlecloud"
    [runners.autoscaler.plugin_config]
      name = "autoscaler-linux"
      zone = "us-central1-c"
    [runners.autoscaler.connector_config]
      username = "ubuntu"
      timeout = "10m0s"
      use_external_addr = true

    [[runners.autoscaler.policy]]
      idle_count = 0 # MODIFY THIS TO 1 WHEN RUNNER IS RUNNING AND SEE CHANGES
      idle_time = "1m"

What are the relevant issue numbers?

Closes #29314 (closed)

Merge request reports