resource quota allocation for a given user/agent
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 48
- Forks
- 10
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 17
Description
Currently, there is no resource quota for the user/agent.
- Define a strategy for resource allocation
- Ensure that the idle resource from one user can be reused by another user but soft-preemptively handed back to the original user when needed.
- Use k8s native architecture such as kueues for allocation
- Resource usage observability of the agent
Contributor guide
No contributing guide indexed for this repository
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 or tests are named. Start by reviewing the repository's existing Kubernetes deployment and agent resource-usage paths, then clarify the allocation strategy and Kueue integration requirements. The work is done when idle resources can be reused, returned to the original user when needed, and usage is observable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, typescript
- Domain
- infrastructure, observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100