actions/actions-runner-controller

Kubernetes controller for GitHub Actions self-hosted runners

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 15 minutes ago
Added to GitGenius on September 10th, 2026
Created on January 28th, 2020
Open Issues & Pull Requests: 398 (+0)
GitHub issues: Enabled
Number of forks: 1,472
Total Stargazers: 6,492 (+0)
Total Subscribers: 70 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 47.6 hours
Mean response time: 32.9 days
90th percentile: 85.5 days
Tracked items: 399

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 97% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Only 4% of issues opened in the past year have been closed. Three people close 76% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 115
New in 7 days: 6
Closed in 7 days: 8
Avg open age: 699 days
Stale 30+ days: 90
Stale 90+ days: 73

Recent activity

Opened in 7 days: 6
Closed in 7 days: 8
Comments in 7 days: 2
Events in 7 days: 5

Top labels

  • needs triage (312)
  • bug (296)
  • gha-runner-scale-set (260)
  • community (82)
  • enhancement (78)
  • stale (17)
  • question (7)
  • attention (2)

Detailed Description

Actions Runner Controller is a Kubernetes operator that orchestrates and scales self-hosted runners for GitHub Actions.

The tool addresses the challenge of managing compute resources for GitHub Actions workflows by automating runner provisioning and scaling within Kubernetes clusters. It creates runner scale sets that automatically adjust the number of active runners based on workflow demand across repositories, organizations, or enterprises. Because runners are container-based and ephemeral, they can scale up or down rapidly without leaving residual state, and new instances can be deployed cleanly as needed.

Teams running GitHub Actions at scale should adopt this tool if they already operate Kubernetes infrastructure and want to avoid the operational burden of manually managing runner capacity. It suits organizations that need predictable cost control through dynamic scaling and those running workflows with variable demand patterns. The project distinguishes itself by providing native Kubernetes integration through a standard operator pattern, allowing configuration via Helm and native Kubernetes resources rather than external tooling.

Development is shared between the GitHub Actions team and community maintainers, with active discussion channels for users to report issues and propose features. The project maintains both current autoscaling runner scale sets and legacy autoscaling modes, with the legacy modes explicitly designated as community-maintained while the newer approach receives primary support. Documentation is centralized on the official GitHub documentation site rather than maintained separately in the repository.