actions / actions/actions-runner-controller
Facilitate detection of failed pod creation
Open
Nobody has claimed this yet.
community
enhancement
- Dominant language
- Go
- Stars
- 6.5k
- Forks
- 1.5k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 27
Description
What would you like added?
When the runner controller fails to create a pod, I want to be able to see the error only with runner view permissions.
Why is this needed?
If I don't have permission to view the runner controller logs, there is no way to determine if the creation of the pod for runner failed.
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
The issue names no files, tests, or entry points; start by tracing pod creation failures in the Go controller and how runner-view permissions expose status. Done means a user with runner view permissions can determine that pod creation failed without access to controller logs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- authorization, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100