Multi-cloud, auto-scaling manager for GitHub Actions & Gitea self-hosted runners with pluggable providers
-
Updated
Jun 9, 2026 - Go
Multi-cloud, auto-scaling manager for GitHub Actions & Gitea self-hosted runners with pluggable providers
In this project, we present a complete and practical DevOps project that shows how to run self-hosted GitHub Actions runners as Kubernetes pods that spin up on demand, execute a CI job, then terminate.
A native macOS menu bar app that orchestrates ephemeral GitHub Actions runners on Apple Silicon using Tart VMs
On-demand, ephemeral Forgejo Actions runners on cloud VMs — kept warm only for the billing hour you've already paid for, so you never pay for idle CI.
Lightweight Github Actions controller for GCE spot instances
Ansible bootstrap for k3s install + K8s manifests for Flask container deploy. Workflows run on ephemeral self-hosted runners managed by ARC inside the k3s cluster. Part of a three-repo CI/CD/CD design - see ARCHITECTURE.md
Multi-tenant Kubernetes operator for self-hosted GitHub Actions runners. Scale-to-zero workers, per-tenant egress IP pools, and GPU priority scheduling across a shared ResourceQuota — an Actions Runner Controller (ARC) alternative.
Add a description, image, and links to the ephemeral-runners topic page so that developers can more easily learn about it.
To associate your repository with the ephemeral-runners topic, visit your repo's landing page and select "manage topics."