actions / actions/runner-container-hooks
[New Feature request] New no-volumes implementations removes node affinity features
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 153
- Forks
- 112
- Avg merge
- 6m
- Merged PRs (30d)
- 1
Description
Previously, it was possible to co-allocate to the same node subsequent jobs.
Given the new method of using a stream to communicate the working folder content, it would be nice to re-implement the node-affinity scheduling to be able to tell ARC to co-locate these pods if necessary.
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 tracing the no-volumes stream implementation and the existing node-affinity scheduling path. Define how ARC should request co-location for subsequent jobs and verify that pods are scheduled on the same node when needed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, kubernetes, typescript
- Domain
- ci-cd, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100