GitHub Actions Self-Hosting Runners in k8s
summary
Shows how to deploy actions-runner-controller and cert-manager into a local kind Kubernetes cluster to register repository- and organization-level self-hosted GitHub Actions runners. Demonstrates running workflows where the controller auto-scales runners via a Horizontal Runner to at least five replicas, recreates pods per job, and reuses PVCs to speed repeated jobs. Notes practical limits: free minute billing tiers (≈2,000–3,000 minutes, Enterprise 50,000), workflow/action timeouts (72h workflow, 24h per action), and GitHub API rate caps.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 1:30GitHub Actions in CI/CD
- 5:27Plans and limits
- 7:39Self-hosted runners
- 9:24Kubernetes runner setup
- 10:26actions-runner-controller
- 13:15Controller vs operator
- 16:50Demo setup
- 23:19Repo-level runners
- 26:56Running workflows
- 28:46Org-level runner management
- 30:57Runner groups
- 34:55Horizontal scaling
- 37:50Autoscaling metrics
- 41:06Advanced labels
- 42:50GitHub Actions limits
- 44:16Costs and multipliers
- 45:41Spot instances
- 46:45Summary
related talks
41mSecuring Self-Hosted GitHub Actions with Kubernetes & Actions-Runner-Controller
05m⚡️Lightning Talk: Github Actions on Kubernetes
36mRunning the Runners: How CNCF Powers GitHub Actions at Scale
34mRunning the Runners: How CNCF Powers GitHub Actions at Scale
50mGitHub Actions in action
37mGitHub Actions + K8S to level up software dev
30mPragmatic, scalable, and ergonomic CI/CD using Github Actions and K8s.
30mSpend More Time Coding & Automate the Boring Stuff