While public runners are an efficient way of getting your GitHub workflows up and running, there are scenarios where you cannot use them. Be it regulatory, security, or just performance, there is a fair chance that you have to deploy your own actions runners at some point.

One of the main benefits of Kubernetes is that it scales, the drawback is that it can be a pain to configuration. But we in the cloud native community are masters at abstractions, and by adding controllers or operators we can easily automate away the pain.

Let us take a good look at the Actions Runner Controller from GitHub, an efficient way of deploying self-hosted runners.