actions / actions/actions-runner-controller
Label runner pod with the current job running on it
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?
Update the labels on the runner pod to include the current job name and id whenever a job is assigned to a pod and remove it when the job exits.
Why is this needed?
We would like better insights into which jobs are accurately sized for our different worker classes. If ARC could update the labels on a runner pod with the name or id of the job that is currently running on it, that would allow us to aggregate metrics based on the historical performance of jobs in different worker configurations
Additional context
Pods do not need to be restarted when the only change is the label. Prometheus and other tools can collect and filter metrics on pods based on the current labels
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 runner pod lifecycle from job assignment through job exit, focusing on the controller entry points that update pod metadata. Verify how pod labels are currently managed and test that the current job name and ID appear while a job runs, are removed afterward, and do not trigger a pod restart.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, go, kubernetes
- Domain
- ci-cd, devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100