actions / actions/actions-runner-controller
support multiple repositories with array in crd RunnerDeployment
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 6.5k
- Forks
- 1.5k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 27
Description
What would you like added?
in RunnerDeployment there is a general requirement to support multiple repository since it's more safe than organization level, but from current crd description https://github.com/actions/actions-runner-controller/blob/master/charts/actions-runner-controller/crds/actions.summerwind.dev_runnerdeployments.yaml#L3366, only string type is supported, we need to create multiple RunnerDeployment to add different repository instead of add a array in one RunnerDeployment spec.
is that ok to update repository string type to repositories array type?
Note: Feature requests to integrate vendor specific cloud tools (e.g. awscli, gcloud-sdk, azure-cli) will likely be rejected as the Runner image aims to be vendor agnostic.
Why is this needed?
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
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
Start with the RunnerDeployment CRD at charts/actions-runner-controller/crds/actions.summerwind.dev_runnerdeployments.yaml around line 3366, then trace how the repository field is consumed. Determine the required schema and controller behavior for multiple repositories, and verify that a RunnerDeployment can target each requested repository without breaking existing string-based configurations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- ci-cd, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100