actions / actions/actions-runner-controller
IssueOps to control creation/scaling/deletion of runner deployments and visualization of matrix builds
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 6.5k
- Forks
- 1.5k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 27
Description
👋 @mumoshu @summerwind,
I came up with an IssueOps driven approach to configure deployments with this ✨ actions-runner-controller ✨: https://github.com/jonico/auto-scaling-github-runners-kubernetes-issueops
Here is a three minute minute showing the project in action:
Furthermore, I took the matrix build idea literally and build a visualisation of matrix builds with your controller:
https://youtu.be/21LQdeuvPng (visualization code is here)
If you feel it makes sense to link those projects in your documentation, feel free to do so.
:octocat: ❤️
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the repository documentation alongside the linked IssueOps and matrix-build projects. Done means deciding whether those projects belong in the documentation and, if so, adding appropriate links; no specific file or test is named in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, kubernetes
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 32/100