actions / actions/actions-runner-controller
RunnerSet support for IRSA roles
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?
Currently, setting serviceAccountName on a RunnerSet does not mount a generated token from EKS when creating a runner; however it does do so when using a RunnerDeployment
Why is this needed?
I make heavy use of RunnerSet's ephemeral volume provisioning which is currently unavailable on RunnerDeployment's, making it a decision between supporting workspace volumes or IRSA capabilities
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
Compare the RunnerSet and RunnerDeployment paths that handle serviceAccountName and generated EKS tokens, then trace how RunnerSet ephemeral volume provisioning is reconciled. Confirm the behavior against a Kubernetes RunnerSet using an IRSA role; done means the runner receives the generated token without losing ephemeral volume support.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, github-actions, go, kubernetes
- Domain
- authentication, ci-cd, cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100