Sometimes you just need a little human interaction. And sometimes you need that to happen when you’re starting up a dev container so you can configure the environment. Thankfully, there is a way to get user input that works with most of the dev container implementations.

Ever needed to automate creating an Azure Entra ID (Azure Active Directory) application and federating it with GitHub? With just a little PowerShell, you can!

Continuing the discussion from last week, here are a few additional recommendations that can improve your ability to manage and scale your ARC deployments.

There are some common issues that lead to teams struggling to set up ARC. Nearly all of these can be avoided by following a few simple guidelines. In the first of a two-part post, I’ll outline some of my recommendations for improving your experience setting up ARC.

GitHub ARC is a great way to run your GitHub Actions runners in your own Kubernetes cluster. ARC has its own set of requirements and best practices. One of the most important best practices I recommend is to use a dedicated Kubernetes cluster. This post will explain why.