vllm-project / vllm-project/production-stack
Discussion: Unifying versions for helm and router
Open
Nobody has claimed this yet.
question
- Dominant language
- Python
- Stars
- 2.6k
- Forks
- 503
- Avg merge
- 4d 17h
- Merged PRs (30d)
- 8
Description
Currently, the stack version in the router is hard-coded at this line.
The Helm chart has its own version management. Should we maintain separate versions for different components, or just use the same version across the board?
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 src/vllm_router/router.py at line 32, then locate the Helm chart's version-management files. Compare how the router and chart currently obtain and use their versions. Done means the project has a decided policy on shared versus separate versions and the affected locations are identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, python
- Domain
- devops, release
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100