actions-runner-controller VS helm-charts

To set-up the self-hosted runner, an Action Runner Controller (ARC) and Runner scale sets application will be installed via helm. This post will be using Azure Kubernetes Service and ARC that is officialy maintained by Github. There is another ARC that is maintained by the community. You can follow the discussion where github adopted the ARC project into a full Github product here

Before this we were using https://github.com/actions/actions-runner-controller but that's running on K8s instead of VMs. So along with common limitations of running CI jos in K8s/container, it cannot have exactly the same environment as the official GitHub runners. Maintaining a K8s cluster was also very difficult.

ARC is great for running GitHub Actions on Kubernetes:

https://github.com/actions/actions-runner-controller

Almost all of our cicd, builds run on GitHub. I'm talking cypress tests, deployments via terraform and helm to over 25 environments, all backend tests, daily test runs etc. Overall we were racking up a cost of almost 20k on GitHub. With the ARC deployed and using spot instances I think our total infrastructure costs went up about 4-5k even though we added more actions. If we switched back to their runners we'd probably be around 25k at this point.

What else needs to be moved to my artifactory (charts - https://github.com/actions/actions-runner-controller/tree/master/charts ) - if so tar or entire folder or anything else ? ) What should the above steps correspond to?

You need to use the steps in the repo instead of the steps on the docs if you're using enterprise server.

Honestly not a fan of Github docs.....I feel like the ones in the repo are much clearer and easier to understand/read.

Its pretty easy to set up honestly. Deploy this on your k8s cluster https://github.com/actions/actions-runner-controller and a runnerDeployment and youre good to go.

Trying to use the Actions Runner Controller (https://github.com/actions/actions-runner-controller) to utilize self-hosted runners. I keep getting this error on the controller.

I'm convinced one of (or a combination) of things is happening here in regards to authentication. This GH enterprise account is configured with SAML. I feel like that is a valid data point. I'm using https://github.com/actions/actions-runner-controller as a reference guide for what I should be doing. I suspect whoever is Owner of this organization has modified what I can do as a user. The steps in the doc where I can actually Install the Application isn't available to me. When configuring the GitHub App I'm given two options. I select the option for "this account only" knowing the documentation says it is possible to use this Github App with a repo in the Organization as long as I have Admin privileges or I'm the owner.

I have no clue of what is wrong. The applicationset yaml looks like (somewhat cut-down): apiVersion: argoproj.io/v1alpha1 kind: ApplicationSet metadata: name: myjenkins namespace: argocd spec: generators: - list: elements: - namespace: "development" ingressHostName: "myjenkins-dev.scs.domain" limitsMemory: "12Gi" template: metadata: name: myjenkins spec: destination: namespace: '{{namespace}}' server: https://kubernetes.default.svc project: default syncPolicy: {} sources: - chart: jenkins repoURL: https://github.com/jenkinsci/helm-charts/tree/main/charts targetRevision: 4.3.9 helm: releaseName: myjenkins parameters: - name: extraLabels value: slice1 - name: controller.resources.limits.cpu value: '8' - name: controller.resources.limits.memory value: '{{limitsMemory}}' valueFiles: - $values/deployments/jenkins/global/common.values - $values/deployments/jenkins/global/shared-libs.values - $values/deployments/jenkins/global/job-dsl-seed.values - $values/deployments/jenkins/global/ssh-credentials.values - $values/deployments/jenkins/global/kubernetes-cloud.values - repoURL: 'ssh://[email protected]:29418/kubernetes' targetRevision: master ref: values

Here is what I'm deploying.. I have a very small GKE cluster up and running right now with terraform. I'm on a budget, so I'm trying to containerize as many of the services we need for development as possible. I am using this Jenkins helm chart for deployment: https://github.com/jenkinsci/helm-charts/blob/main/charts/jenkins/README.md

I've updated my post with the error logs and some descriptions. The "Additional Agents" thing is part of the Helm chart. The Adding Pod Templates Using additionalAgents section of the Helm Chart's README gives an example of how to declare them. I initially tried using a direct copy of the example in the README (adapted to use with the Ansible module) but that displayed roughly the same behaviour

https://github.com/jenkinsci/helm-charts/tree/main/charts/jenkins Using offical chart