mayadata-io / mayadata-io/d-operators
feat: use client.go's retry instead of continuous polls to api server
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 10
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
Recipe/Job custom resource makes continuous requests to API server. This can exhaust kubernetes API server. Use client-go' retry to reduce this attack on api server.
In addition, to above make use of Get & List calls of Informer. This should also help reduce exhausting kubernetes api server.
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 with the referenced client-go retry example and trace how the Recipe/Job custom resource currently requests the API server. Check the controller's informer usage, then replace continuous polling with client-go retry and informer Get/List calls. Done means the resource reconciliation no longer makes continuous API requests while still observing updates correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- backend-api-design, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100