When the Runner ScaleSet Listener receives the Job Available message, it checks whether it can scale up to the desired count.When a workflow run is triggered from a repository, the GitHub Actions Service dispatches individual job runs to the runners or runner scalesets where the runs-on key matches the name of the runner scaleset or labels of self-hosted runners.The listener stays idle until it receives a Job Available message from the GitHub Actions Service. In this pod, the listener application connects to the GitHub Actions Service to authenticate and establish an HTTPS long poll connection. A Runner ScaleSet Listener pod is deployed by the AutoScalingListener Controller.The AutoScalingRunnerSet Controller calls the APIs one more time to either fetch or create a runner scale set in the GitHub Actions service before creating the Runner ScaleSet Listener resource.The AutoScalingRunnerSet Controller calls GitHub's APIs to fetch the runner group ID that the runner scale set will belong to.

A new AutoScalingRunnerSet resource is deployed via the supplied Helm charts or a customized manifest file. Actions Runner Controller is installed using the supplied Helm charts, and the controller manager pod is deployed in the specified namespace.Note: To view the following diagram in a larger size, see the Autoscaling Runner Scale Sets mode documentation in the Actions Runner Controller repository.

Download ArcRunner free