Go to file
Gunju Kim 4ef74591dc ubuntu-22.04: Install net-tools package to update the dockerMTU 2024-06-19 17:45:23 +09:00
.github Prepare 0.9.2 release (#3530) 2024-05-20 10:58:06 +02:00
acceptance
apis Fix overscaling when the controller is much faster then the listener (#3371) 2024-03-20 15:36:12 +01:00
build
charts Prepare 0.9.2 release (#3530) 2024-05-20 10:58:06 +02:00
cmd Refresh session if token expires during delete message (#3529) 2024-05-17 15:16:38 +02:00
config Fix overscaling when the controller is much faster then the listener (#3371) 2024-03-20 15:36:12 +01:00
contrib
controllers Remove `.Named()` from the ephemeral runner controller (#3596) 2024-06-17 10:36:08 +02:00
docs Prepare 0.9.2 release (#3530) 2024-05-20 10:58:06 +02:00
github Propagate max capacity information to the actions back-end (#3431) 2024-04-16 14:00:40 +02:00
hack
hash
logging
pkg
runner ubuntu-22.04: Install net-tools package to update the dockerMTU 2024-06-19 17:45:23 +09:00
simulator
test Bump Go patch version to 1.22.4 (#3593) 2024-06-17 10:36:23 +02:00
test_e2e_arc
testing Bump Go patch version to 1.22.4 (#3593) 2024-06-17 10:36:23 +02:00
.dockerignore
.gitattributes
.gitignore
.golangci.yaml Extract single place to set up indexers (#3454) 2024-05-17 14:42:46 +02:00
CODEOWNERS Add Francesco (@rentziass) to CODEOWNERS (#3362) 2024-03-18 12:08:16 +01:00
CODE_OF_CONDUCT.md
CONTRIBUTING.md
Dockerfile Bump Go patch version to 1.22.4 (#3593) 2024-06-17 10:36:23 +02:00
LICENSE
Makefile Updates: runner to v2.317.0 (#3559) 2024-06-07 11:53:30 +02:00
PROJECT
README.md
SECURITY.md
TROUBLESHOOTING.md
go.mod Bump Go patch version to 1.22.4 (#3593) 2024-06-17 10:36:23 +02:00
go.sum Bump golang.org/x/sync from 0.6.0 to 0.7.0 (#3482) 2024-04-30 08:53:19 +02:00
main.go Extract single place to set up indexers (#3454) 2024-05-17 14:42:46 +02:00

README.md

Actions Runner Controller (ARC)

CII Best Practices awesome-runners Artifact Hub

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.

In case you are already the employer of one of contributors, sponsoring via GitHub Sponsors might not be an option. Just support them in 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

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.