Hacker News Reader

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.

View on HN

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.

Reply on news.ycombinator.com