actions / actions/runner-container-hooks
Implement retries and back off when talking to the kubernetes API
Open
Nobody has claimed this yet.
enhancement
k8s
- Dominant language
- TypeScript
- Stars
- 153
- Forks
- 112
- Avg merge
- 6m
- Merged PRs (30d)
- 1
Description
Based on the issue in ARC, large workflows can encounter the occasional failures due to the lack of retries when communicating with the Kubernetes API server.
Implementing retries with the back off can lower the amount of failures due to the communication issues
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
No files, tests, or entry points are named. Read the linked ARC issue first, then trace where this repository communicates with the Kubernetes API and determine an appropriate retry and backoff behavior. Done means intermittent API communication failures are retried with backoff and the relevant behavior is covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, typescript
- Domain
- api, devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100