🚀 On-Demand GitHub Actions Runners w/ Kubernetes Pods | Full DevOps Project Walkthrough
GitHub Repo: https://github.com/iQuantC/EphemeralP...
Description
In this video, we take you step-by-step through setting up self-hosted GitHub Actions runners that spin up inside Kubernetes pods on demand, execute CI/CD jobs, and then gracefully shut down. This modern DevOps pattern gives you ephemeral, isolated, and cost-efficient CI/CD infrastructure that scales seamlessly with your workloads.
🔹 What you’ll learn in this video:
1. What self-hosted GitHub Actions runners are and why you’d want to run them in Kubernetes.
2. Installing and configuring Actions Runner Controller (ARC) using Helm.
3. Setting up runner scale sets for ephemeral, job-specific pods.
3. Authenticating with GitHub via PATs (and the GitHub App approach).
4. Running a real GitHub Actions workflow on the Kubernetes-managed runners.
5. Watching pods spin up and terminate automatically after the job completes.
🔹 Why this is important
Traditional self-hosted runners stay online 24/7, which can waste resources and introduce security risks. By leveraging Kubernetes and ARC, we unlock elastic, secure, and cloud-native CI/CD pipelines — only paying for compute when jobs are actually running.
🔹 Tech Stack Covered:
1. Kubernetes (local cluster / cloud)
2. Helm
3. Actions Runner Controller (ARC)
4. GitHub Actions
5. GitHub PAT / App authentication
Whether you’re a DevOps engineer, SRE, or a developer exploring modern CI/CD patterns, this project will help you understand how to bring enterprise-grade scalability to your GitHub workflows.
👉 If you enjoy this kind of deep-dive DevOps project, don’t forget to like, share, and subscribe for more hands-on tutorials!
#GitHubActions #Kubernetes #SelfHostedRunner #DevOps #CICD
Happy DevOpsing!