Running GitHub Self-Hosted Runners on AKS Virtual Nodes (backed by Azure Container Instances)

GitHub Self-Hosted Runners let you use your environments with GitHub Actions for automations of all sorts, like building and deploying software (CI/CD), running tests, and all sorts of goodies. One popular approach is using runners hosted in containers and running these on Kubernetes. GitHub even provides a controller that can scale your runners based on jobs on GitHub. With Azure Kubernetes Services (AKS), you can run self-hosted containers, too—even on virtual nodes, which use Azure Container Instances (ACI). This offers on-demand runners for your build needs that scale dynamically with the demand of your jobs. In this video we’ll explain how all this works, show you how to set it up, and then deploy a GH Action that spins up a runner, executes the jobs, then deallocates when finished.

Manifest Code Sample: https://github.com/theonemule/dos-gam...

Installing the Action Runner Controller

helm repo add jetstack https://charts.jetstack.io
helm repo update
helm install cert-manager jetstack/cert-manager --namespace cert-manager --create-namespace --version v1.10.1 --set installCRDs=true

helm repo add actions-runner-controller https://actions-runner-controller.git...
helm repo update
helm upgrade --install --namespace actions-runner-system --create-namespace --set=authSecret.create=true --set=authSecret.github_token="" --wait actions-runner-controller actions-runner-controller/actions-runner-controller



----------------

Atmosera: https://www.atmosera.com/
WintellectNOW: https://www.wintellectnow.com/
Blaize's Website: https://www.blaize.net/

Twitter:

Blaize:   / theonemule  
Atmosera:   / atmosera  
WintellectNOW:   / wintellectnow