actions / actions/actions-runner-controller
Cache to disk: EBS volumes in EKS
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?
I would like to be able to cache docker images and other parts of the build process to a disk.
Why is this needed?
To speed up builds and skip repetitive steps.
Additional context
Seems like this has been widely talked about in this project, but the newest version of RunnerSet behaves more like a deployment than a StatefulSet, which makes re-using disks in AWS difficult. I imagine if the RunnerSet or AutoscalingRunnerSet used a StatefulSet, we could re-use specific disks...
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 by reading how RunnerSet and AutoscalingRunnerSet are implemented and how they create runner workloads in EKS. Compare their current behavior with the StatefulSet behavior described in the issue, then determine the expected lifecycle for EBS-backed disk reuse and how Docker image and build caches should persist. Done means a documented, tested approach for reusing disks while preserving runner autoscaling behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, github-actions, go, kubernetes
- Domain
- ci-cd, cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100