In the past, ARC has a feature that enabled it to change the minimum number of runners based on a schedule: ScheduledOverrides. When ARC was modernized, this feature was not included in the new version. This isn’t an oversight. Instead, it’s a recognition that Kubernetes has a built-in feature that can handle this task: CronJob. Learn how to use the CronJob resources to change the settings for ARC scale sets on a schedule.

A surprising amount of effort (and automation) goes into creating this blog and publishing the content. Writing and hosting content required me to find a set of tools that would be portable and flexible. Over the last few years I’ve found an approach that works for me, and this week I thought I’d share some of the details.

Actions Runner Controller (ARC) is a powerful way to manage ephemeral, self-hosted GitHub runners. If you’re considering ARC or starting to deploy it, there are five key things to know if you want to be successful using it.

There’s a lot happening under the covers with Kubernetes. If you really want to master your Kubernetes environment, it begins with understanding the value of a logging and how to implement good logging practices.

Scaling systems is a process that is often counter-intuitive. It’s not just about adding more resources. It’s about understanding the bottlenecks and how to overcome them. After years spent troubleshooting highly scaled systems, I’ve learned a few things that can make the journey easier.