Nikola JokicandCopilot App
55f1ad560b
Follow-up review of the metadata validation surfaced four gaps: Listener pod metadata took the same unvalidated, uncoerced path that the runner pod metadata used to: an invalid label only failed once the controller created the listener pod, which is the silent failure mode this change set exists to remove. Both charts now validate it at render time and route its values through the string coercion. Values loaded from a values file arrive as float64, so "%v" rendered a large integer such as 12345678901234 in scientific notation, silently corrupting the annotation. Integral floats are now formatted without an exponent, and the remaining sites that quoted metadata values directly go through the same helper. A map or list value was flattened into Go's own formatting, producing a meaningless "map[a:b]" label. Such values are now rejected with the values path that produced them. The label key prefix check rejected dot-separated segments longer than 63 characters. Kubernetes only bounds the prefix at 253 characters in total, so the check was stricter than the API server and would have rejected keys that already work. While covering the listener path, the experimental chart turned out to render invalid YAML whenever listener.podTemplate carried both metadata and spec: the last metadata value and the following "spec:" key ended up on the same line. That is fixed here too, with a regression test. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Actions Runner Controller (ARC)
About
Actions Runner Controller (ARC) is a Kubernetes operator that orchestrates and scales self-hosted runners for GitHub Actions.
With ARC, you can create runner scale sets that automatically scale based on the number of workflows running in your repository, organization, or enterprise. Because controlled runners can be ephemeral and based on containers, new runner instances can scale up or down rapidly and cleanly. For more information about autoscaling, see "Autoscaling with self-hosted runners."
You can set up ARC on Kubernetes using Helm, then create and run a workflow that uses runner scale sets. For more information about runner scale sets, see "Deploying runner scale sets with Actions Runner Controller."
People
Actions Runner Controller (ARC) is an open-source project currently developed and maintained in collaboration with the GitHub Actions team, external maintainers @mumoshu and @toast-gear, various contributors, and the awesome community.
If you think the project is awesome and is adding value to your business, please consider directly sponsoring community maintainers and individual contributors via GitHub Sponsors.
If you are already the employer of one of the contributors, sponsoring via GitHub Sponsors might not be an option. Just support them by other means!
See the sponsorship dashboard for the former and the current sponsors.
Getting Started
To give ARC a try with just a handful of commands, please refer to the Quickstart guide.
For an overview of ARC, please refer to About ARC.
With the introduction of autoscaling runner scale sets, the existing autoscaling modes are now legacy. The legacy modes have certain use cases and will continue to be maintained by the community only.
For further information on what is supported by GitHub and what's managed by the community, please refer to this announcement discussion.
Documentation
ARC documentation is available on docs.github.com.
Legacy documentation
The following documentation is for the legacy autoscaling modes that continue to be maintained by the community:
- Quickstart guide
- About ARC
- Installing ARC
- Authenticating to the GitHub API
- Deploying ARC runners
- Adding ARC runners to a repository, organization, or enterprise
- Automatically scaling runners
- Using custom volumes
- Using ARC runners in a workflow
- Managing access with runner groups
- Configuring Windows runners
- Using ARC across organizations
- Using entrypoint features
- Deploying alternative runners
- Monitoring and troubleshooting
Contributing
We welcome contributions from the community. For more details on contributing to the project (including requirements), please refer to "Getting Started with Contributing."
Troubleshooting
We are very happy to help you with any issues you have. Please refer to the "Troubleshooting" section for common issues.