We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Background Having 4 permanent runners is cool and all, but we need to think about:
The Solution Utilize runners that are ephemeral (the runner is created and destroyed as needed) and autoscaling (the amount of runners at any one time conform to the workload). We can achieve this using Kubernetes and a GitHub-created runner controller called the Actions Runner Controller. See here: https://docs.github.com/en/actions/hosting-your-own-runners/managing-self-hosted-runners/autoscaling-with-self-hosted-runners
Considerations
Tagging @jo-basevi as she has had some Kubernetes experience
References ACCESS-NRI/build-ci#5
The text was updated successfully, but these errors were encountered:
Update for today:
kubectl
alias kubectl="minikube kubectl --"
~/.bashrc
Sorry, something went wrong.
jo-basevi
No branches or pull requests
Background
Having 4 permanent runners is cool and all, but we need to think about:
The Solution
Utilize runners that are ephemeral (the runner is created and destroyed as needed) and autoscaling (the amount of runners at any one time conform to the workload). We can achieve this using Kubernetes and a GitHub-created runner controller called the Actions Runner Controller.
See here: https://docs.github.com/en/actions/hosting-your-own-runners/managing-self-hosted-runners/autoscaling-with-self-hosted-runners
Considerations
Tagging @jo-basevi as she has had some Kubernetes experience
References ACCESS-NRI/build-ci#5
The text was updated successfully, but these errors were encountered: