vllm-project / vllm-project/production-stack
Pluggable Router Implementations
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
I currently use a Gateway API implementation with an inference extension to perform similar functionality as the vLLM router. I would like to use vllm-stack but with my current router implementation. Will you consider integrating with inference extension as a supported router implementation?
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
No files, tests, or entry points are named. First clarify how vllm-stack should integrate the Gateway API inference extension, then define supported-router behavior and validation criteria before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, python
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100