vllm-project / vllm-project/production-stack
feature: crd ressources : split request and limit ressources
Open
Nobody has claimed this yet.
feature request
- Dominant language
- Python
- Stars
- 2.6k
- Forks
- 503
- Avg merge
- 4d 17h
- Merged PRs (30d)
- 8
Description
Describe the feature
Hi
In the CRD,limit and request ressources use the same variables.
Why do you need this feature?
Use differents values for request and limit ressources
Additional context
No response
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 by locating the CRD resource definitions where request and limit resources currently use the same variables. Trace how those values are passed into the deployment configuration, then separate the request and limit inputs and verify that each can receive a different value.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100