mayadata-io / mayadata-io/d-operators
performance: ensure most get and list operations are from shared cache
Open
Nobody has claimed this yet.
benchmark
performance
- Dominant language
- Go
- Stars
- 10
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
ProblemStatement: As a Kubernetes admin, I want operators that do not exhaust Kubernetes API server with a deluge of requests. I want d-operators to reduce its interaction with Kubernetes API server substantially without impacting the way its controllers work.
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. First identify where get and list operations interact with the Kubernetes API server and how shared caching is currently handled; done means substantially fewer API requests without changing controller behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- infrastructure, performance
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100