GitHub Actions Runner Scale Set Controller Helm Chart
The GitHub Actions Runner Scale Set Controller Helm chart automates deployment and configuration of the Actions Runner Controller (ARC) in Kubernetes clusters using Minimus images. ARC enables autoscaling of self-hosted GitHub Actions runners on Kubernetes.
Prerequisites
- A subscription to the Minimus images included in the chart
- A running Kubernetes cluster (v1.21 or higher is recommended)
kubectl installed and configured- Helm v3.8 or higher for OCI support (Installation instructions)
- Cluster Admin privileges
Note: The controller installs Custom Resource Definitions (CRDs) required for managing AutoscalingRunnerSet, AutoscalingListener, EphemeralRunner, and EphemeralRunnerSet resources.
Try It Out
In this example we will deploy the Actions Runner Controller on a Kubernetes cluster using the Minimus GitHub Actions Runner Scale Set Controller Helm chart. The controller manages the lifecycle of self-hosted GitHub Actions runner scale sets.
Step 1: Start Cluster
If you have a cluster to work with, skip this step. Otherwise, start a Minikube cluster. Deployment instructions
Step 2: Create Namespace
Create a namespace:
kubectl create ns gha-runner-scale-set-controller
Step 3: Deploy the Helm Chart
Deploy the Minimus Helm chart:
helm install my-gha-runner-scale-set-controller oci://helm.mini.dev/gha-runner-scale-set-controller \
--version 0.14.2 \
-n gha-runner-scale-set-controller \
--wait
If you want to override the chart's defaults, go to the Values tab, save a copy locally with your changes. Deploy the chart with your overrides using -f values.yaml:
helm install my-gha-runner-scale-set-controller oci://helm.mini.dev/gha-runner-scale-set-controller \
--version 0.14.2 \
-f values.yaml \
-n gha-runner-scale-set-controller \
--wait
Step 4: Verify GitHub Actions Runner Scale Set Controller is Running
Confirm the chart deployed successfully and the controller started:
kubectl get pods -n gha-runner-scale-set-controller
You should see output similar to:
NAME READY STATUS RESTARTS AGE
my-gha-runner-scale-set-controller-xxxxxxxxx-xxxxx 1/1 Running 0 2m
Step 5: Verify CRDs are Installed
Confirm the Custom Resource Definitions were installed:
kubectl get crds | grep actions.github.com
You should see CRDs for autoscalingrunnersets, autoscalinglisteners, ephemeralrunners, and ephemeralrunnersets:
autoscalinglisteners.actions.github.com 2025-01-01T00:00:00Z
autoscalingrunnersets.actions.github.com 2025-01-01T00:00:00Z
ephemeralrunners.actions.github.com 2025-01-01T00:00:00Z
ephemeralrunnersets.actions.github.com 2025-01-01T00:00:00Z
Step 6: Clean Up
Uninstall the chart and delete the namespace to remove all resources:
helm uninstall my-gha-runner-scale-set-controller -n gha-runner-scale-set-controller
kubectl delete namespace gha-runner-scale-set-controller
Terms & Info
Trademark
This catalog is published by Minimus. All product names, logos, and marks, other than those belonging to Minimus, shown are owned by their respective rights holders and appear here only to identify the open source software each image contains. Minimus claims no ownership of those marks and implies no affiliation with, endorsement by, certification by, or sponsorship by any rights holder.
Disclaimer
Images are provided "as-is" without warranty of any kind. "Hardened" refers to the security configuration applied at the time of build and does not constitute a guarantee of ongoing security or absence of vulnerabilities. The free tier is provided without support, SLA, or guaranteed patching timelines. Security updates may be applied to paid subscriptions before or instead of free tier images. By pulling or using any image you agree to our Terms of Use.
