加载中
正在获取最新内容，请稍候...
GitHub Actions Runner Controller (ARC) for Kubernetes
A Kubernetes controller for self-hosted GitHub Actions runners, enabling dynamic scaling and management of ephemeral runners on your Kubernetes clusters.
Go
Added on 2025年6月30日5,418
Stars1,261
ForksGo
LanguageProject Introduction
Summary
actions-runner-controller (ARC) is a Kubernetes controller that orchestrates and manages GitHub Actions self-hosted runners. It allows you to run your CI/CD workflows on your own infrastructure managed by Kubernetes, providing cost efficiency and greater control.
Problem Solved
Managing self-hosted GitHub Actions runners can be complex, especially in dynamic cloud environments. This controller automates the provisioning, scaling, and lifecycle management of runners directly within Kubernetes, leveraging existing cluster infrastructure and operational practices.
Core Features
Autoscaling
Automatically scale the number of self-hosted runners based on the GitHub Actions workflow queue.
Runner Management
Manage runners as Kubernetes resources (Deployments, StatefulSets) and ensure their lifecycle is tied to workflows.
Ephemeral Runners
Provide ephemeral runners that are created for a single job and discarded afterwards, enhancing security and resource cleanup.
Kubernetes Native Integration
Utilize standard Kubernetes manifests for runner configuration and deployment.
Tech Stack
Kubernetes
Go
GitHub Actions API
Docker
Custom Resource Definitions (CRDs)
Use Cases (使用场景)
The controller is ideal for organizations and teams that need to run their GitHub Actions workflows on self-hosted infrastructure for reasons such as cost optimization, security requirements, or specific hardware/software needs.
Scenario 1: Cost Optimization for Large Scale CI/CD
Details
Organizations running large numbers of GitHub Actions workflows can deploy runners on their cost-optimized Kubernetes clusters instead of using GitHub-hosted runners or manually managed self-hosted runners.
User Value
Significant cost savings by utilizing owned infrastructure and dynamic scaling.
Scenario 2: Running CI/CD in Secured or Private Environments
Details
Teams with specific compliance or security requirements that mandate running CI/CD jobs within their own secured network or data center.
User Value
Compliance with security policies and leveraging private infrastructure.
Scenario 3: Specialized Build Environments
Details
Workflows requiring specific hardware (e.g., GPUs) or complex software setups that are easier to manage as container images deployed on a Kubernetes cluster.
User Value
Flexibility to use custom hardware and environments for specific build/test needs.
Recommended Projects
You might be interested in these projects
YaLTeRniri
Niri is a scrollable-tiling Wayland compositor, designed to provide an efficient and unique window management experience on modern Linux systems.
Rust
9295316
OpenSignLabsOpenSign
OpenSign is a free and open-source alternative to DocuSign, offering secure and legally binding electronic signatures. Streamline your document workflows with a self-hostable and customizable solution.
JavaScript
4745447
get-convexconvex-backend
Convex is the open-source reactive database specifically designed for app developers, simplifying real-time data synchronization and state management in modern applications.
Rust
5508283