Skip to content
New issue

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

Modify the CI Runner to a RunnerDeployment to allow parallel runners? #9

Closed
bjw-s opened this issue Aug 21, 2020 · 2 comments
Closed
Assignees
Labels
question Further information is requested

Comments

@bjw-s
Copy link
Collaborator

bjw-s commented Aug 21, 2020

Currently I have a single Runner (actions-runner-controller) for this repo. Maybe I should modify this to a RunnerDeployment so I can have two parallel runners.

@bjw-s bjw-s added question Further information is requested CI labels Aug 21, 2020
@bjw-s bjw-s self-assigned this Aug 21, 2020
@onedr0p
Copy link
Contributor

onedr0p commented Aug 24, 2020

I was thinking about doing this as well! I don't think it would be a difficult change. I only haven't done it yet because I don't have any jobs that run concurrently on this runner in my CI.

@bjw-s
Copy link
Collaborator Author

bjw-s commented Aug 24, 2020

Done :) See https://github.com/bjw-s/k8s-gitops/blob/master/deployments/actions-runner-system/actions-runner-system/runners/runnerdeployment-gitops.yaml

Added in autoscaling for now, but might revert to fixed # of replicas if Flux gets in the way (because replicas has to be set on the RunnerDeployment otherwise it will throw an error)
https://github.com/summerwind/actions-runner-controller/blob/master/README.md#autoscaling

@bjw-s bjw-s closed this as completed Aug 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants