Hacker News Reader

Comment by notduckrabbit | Hacker News Reader

It has never been easier to setup Proxmox, Kubernetes, and Actions Runner Controller (ARC) to do your own CI on old hardware you might otherwise recycle.

View on HN

We ran actions runners ourselves in kubernetes at previous jobs, and at least back then, a lot of the errors came from the github services simply not telling the runners to handle jobs. So in general it didn't matter how much compute you had, they never got scheduled jobs.

ARC protects you from most common kind of Actions incident as seen over last month: GitHub's runner pool running short. Nothing CI-based can protect from an outage in the Actions service itself.

It should be possible to wire another event dispatcher to ARC instead of relying on actions webhooks. That’s the only part that is a true dependency, it should be possible to basically decouple ARC

Ideally yes. As a backup path I've considered Forgejo with a pull mirror and forgejo-runner on Kubernetes but haven't pursued it.

This is good advice for organizations but if you are an individual GitHub user there is no way to have a pool of a few runners available for all of your repositories.

I don't know why but individual users have to create a single instance runner and mate it with exactly one of their repositories.

Converting from an individual user to a GitHub organization is not simple. The docs certainly make it look that way but I have yet to run into anybody that has done so without some form of catastrophic error that requires support to fix

You do not convert an individual user account to a GitHub organization. You create an organization from your personal account then transfer repos to it.

Yep. Proxmox, Kubernetes, ARC, and t3 code threads spawned inside of kata containers is my current workflow.

Reply on news.ycombinator.com