Go to file
Y. Luis 367ee46122
Fixed scaling runners doc link (#2474)
Co-authored-by: Bassem Dghaidi <568794+Link-@users.noreply.github.com>
2023-05-09 14:45:18 -04:00
.github Check release tag version and chart versions during the release process (#2524) 2023-05-03 11:53:42 +02:00
acceptance Revert docker.sock path to /var/run/docker.sock (#2536) 2023-04-27 13:06:35 +09:00
apis Add ImagePullPolicy to the AutoscalingListener, configurable through Manager env (#2477) 2023-04-04 19:07:20 +02:00
build Print Version Number on startup (#1659) 2022-08-23 13:40:16 +09:00
charts Update helm chart to support actions metrics graceful termiantion (#2498) 2023-04-27 13:50:31 +09:00
cmd Get RunnerScaleSet based on both RunnerGroupId and Name. (#2413) 2023-03-15 11:10:09 -04:00
config Revert actions-runner-controller image tag in kustomization to latest (#2522) 2023-04-21 10:59:34 +09:00
contrib Fixed scaling runners doc link (#2474) 2023-05-09 14:45:18 -04:00
controllers Fix GET validation for lowercase http methods (#2497) 2023-04-27 13:22:41 +09:00
docs docs: Update github docs links under `/managing-self-hosted-runners` (#2554) 2023-05-09 14:43:15 -04:00
github Fix for GHES when authorized through GitHub App with GITHUB_URL instead of GITHUB_ENTERPRISE_URL (#2464) 2023-04-27 13:53:22 +09:00
hack Check release tag version and chart versions during the release process (#2524) 2023-05-03 11:53:42 +02:00
hash Introduce new preview auto-scaling mode for ARC. (#2153) 2023-01-17 12:06:20 -05:00
logging Introduce new preview auto-scaling mode for ARC. (#2153) 2023-01-17 12:06:20 -05:00
pkg actions-metrics: Do our best not to fail the whole event processing on no API creds (#2459) 2023-03-31 20:42:25 +09:00
runner Update runner to version 2.304.0 (#2543) 2023-04-28 10:05:46 -04:00
simulator Changes to folder structure to allow multigroups and changed go mod name (#2105) 2022-12-28 09:38:34 +09:00
test Update runner to version 2.304.0 (#2543) 2023-04-28 10:05:46 -04:00
test_e2e_arc Adding e2e workflows to test dind, kube mode and proxy (#2412) 2023-03-15 12:17:11 -04:00
testing Revert docker.sock path to /var/run/docker.sock (#2536) 2023-04-27 13:06:35 +09:00
.dockerignore dockerfile,e2e: Use buildx and cache mounts for faster rebuilds in E2E 2022-03-02 19:03:20 +09:00
.gitignore Check release tag version and chart versions during the release process (#2524) 2023-05-03 11:53:42 +02:00
.golangci.yaml Changes to folder structure to allow multigroups and changed go mod name (#2105) 2022-12-28 09:38:34 +09:00
CODEOWNERS Include nikola-jokic in CODEOWNERS file (#2184) 2023-01-19 08:21:08 -05:00
CODE_OF_CONDUCT.md Add code of conduct 2022-12-13 11:38:01 +00:00
CONTRIBUTING.md Fix broken links in docs (#2144) 2023-01-12 05:37:58 -05:00
Dockerfile Allow custom graceful termination and loadBalancerSourceRanges for the githubwebhook service (#2305) 2023-02-25 14:18:29 +09:00
LICENSE Add LICENSE 2020-01-30 20:12:12 +09:00
Makefile Check release tag version and chart versions during the release process (#2524) 2023-05-03 11:53:42 +02:00
PROJECT Introduce new preview auto-scaling mode for ARC. (#2153) 2023-01-17 12:06:20 -05:00
README.md Update "People" section in README (#2537) 2023-05-04 08:04:42 -04:00
SECURITY.md Add security guidelines and policy 2022-12-13 11:39:39 +00:00
TROUBLESHOOTING.md Documentation corrections (#2116) 2023-02-21 13:40:23 -05:00
go.mod Add new workflows (#2423) 2023-03-23 14:39:37 +00:00
go.sum Update gomega with new ginkgo version (#2373) 2023-03-07 12:05:25 +01:00
main.go Fix docker.sock permission error for non-dind Ubuntu 20.04 runners since v0.27.2 (#2499) 2023-04-17 21:30:41 +09:00

README.md

Actions Runner Controller (ARC)

CII Best Practices awesome-runners Artifact Hub

People

actions-runner-controller 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.

Status

Even though actions-runner-controller is used in production environments, it is still in its early stage of development, hence versioned 0.x.

actions-runner-controller complies to Semantic Versioning 2.0.0 in which v0.x means that there could be backward-incompatible changes for every release.

The documentation is kept inline with master@HEAD, we do our best to highlight any features that require a specific ARC version or higher however this is not always easily done due to there being many moving parts. Additionally, we actively do not retain compatibly with every GitHub Enterprise Server version nor every Kubernetes version so you will need to ensure you stay current within a reasonable timespan.

About

GitHub Actions is a very useful tool for automating development. GitHub Actions jobs are run in the cloud by default, but you may want to run your jobs in your environment. Self-hosted runner can be used for such use cases, but requires the provisioning and configuration of a virtual machine instance. Instead if you already have a Kubernetes cluster, it makes more sense to run the self-hosted runner on top of it.

actions-runner-controller makes that possible. Just create a Runner resource on your Kubernetes, and it will run and operate the self-hosted runner for the specified repository. Combined with Kubernetes RBAC, you can also build simple Self-hosted runners as a Service.

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

For more information, please refer to detailed documentation below!

Documentation

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.