actions-runner-controller
mkdkr
Our great sponsors
actions-runner-controller | mkdkr | |
---|---|---|
31 | 3 | |
4,132 | 354 | |
3.5% | - | |
9.0 | 0.0 | |
4 days ago | almost 3 years ago | |
Go | Shell | |
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
actions-runner-controller
-
Using Kaniko to Build and Publish container image with Github action on Github Self-hosted Runners
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
-
Show HN: DimeRun v2 – Run GitHub Actions on AWS EC2
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.
-
Terraform module for scalable GitHub action runners on AWS
ARC is great for running GitHub Actions on Kubernetes:
There are also official Heml charts available for ARC: https://github.com/actions/actions-runner-controller
I am in the process of setting it up on a cheap Hetzner box. If it works, would be a great deal! You can get a 64 GB RAM box for 35 EUR/mo at server auctions with unlimited traffic. I don't mention CPU or GPU, as typically this isn't a bottleneck for my projects.
Plus, I can configure cache sharing via host-mounted dir. E.g. pnpm cache can be all in one place, and be locally available to pods via a mounted dir. Same for the Docker image cache. This would speed up CI runs and also reduce network traffic by a huge margin.
GitHub Actions effectively has no local caching. There's an action for caching, but it uses a blob storage for cache artifacts. Which then gets network fetched, gzip'ed and gunzip'ed each time, and from my experience this has never been a gain for medium to large npm projects, as they have thousands of small .js files in node_modules, and thus takes a long time to compress and decompress. I think npm edge cache servers are already so optimized and fast, that in my experience almost always it's faster to install from npm directly. I even tested this on AWS, where the cache was stored in S3, in the same region as CodeBuild (CI), and direct installs from npm were still faster by about 30%.
So other than adding more hardware resources, local caching is the only way to significantly speed up GH Actions, from my experience, and thus you must have your runner.
-
Action-runner-controller & Enterprise Git
Older bugs show setting of enterprise URL ( kubectl set env deploy actions-runner-controller -c manager GITHUB_ENTERPRISE_URL=https:// --namespace actions-runner-system) with and values.yml also shows githubEnterpriseServerURL (https://github.com/actions/actions-runner-controller/blob/master/charts/actions-runner-controller/README.md ).
You need to use the steps in the repo instead of the steps on the docs if you're using enterprise server.
-
How to save a fortune with self hosted GitHub runners
GitHub has made it possible to run GitHub Actions using your own self-hosted runners. Thanks to the Actions Runner Controller it is surprisingly easy to run actions in your Kubernetes clusters.
-
How to reduce the cost of GitHub Actions
Since GitHub official has not provided to deploy a Self-hosted runner on Kubernetes, I used the Actions Runner Controller (ARC) project, This project allows rapid deployment of Self-hosted runners through Runner custom resources.
-
DeepFlow uses Spot Instances to speed up GitHub Action exploration
K8s Controller: Kubernetes controller for GitHub Actions self-hosted runner
-
Configure actions-runner-controller with proxy in private EKS cluster
View on GitHub
mkdkr
- Unpopular opinion: CI/CD engines are an awful idea
-
Write Gitlab CI Pipelines in Python Code
My main problem is running the job/step locally and not wait to CI steps to validate some change.
My solution is: https://github.com/rosineygp/mkdkr
I can write somethings like this:
```Makefile
-
Modern CI Is Too Complex and Misdirected
I just put it in a small solution that I can run in a lot of CI platforms.
https://github.com/rosineygp/mkdkr
in another words: https://xkcd.com/927/
What are some alternatives?
helm-charts - Jenkins helm charts
turnstyle - 🎟️A GitHub Action for serializing workflow runs
cache - Cache dependencies and build outputs in GitHub Actions
azure-pipelines-agent - Azure Pipelines Agent 🚀
drone - Gitness is an Open Source developer platform with Source Control management, Continuous Integration and Continuous Delivery. [Moved to: https://github.com/harness/gitness]
ghat - 🛕 Reuse GitHub Actions workflows across repositories
actions-runner-
github-action-tester - Run tests when pull-requests are opened, or commits pushed.
runner - The Runner for GitHub Actions :rocket:
terraform-aws-github-runner - Terraform module for scalable GitHub action runners on AWS
jenkins-std-lib - Bringing the Zen of Python to Jenkins.
kubernetes-plugin - Jenkins plugin to run dynamic agents in a Kubernetes/Docker environment