vllm-project / vllm-project/production-stack
feature: allow multiple api keys in `servingEngineSpec.vllmApiKey`
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2.6k
- Forks
- 503
- Avg merge
- 4d 17h
- Merged PRs (30d)
- 8
Description
Describe the feature
I want to be able to:
helm install vllmstack vllm/vllm-stack \
--set servingEngineSpec.vllmApiKey="key1,key2,..."
or
helm install vllmstack vllm/vllm-stack \
--set routerSpec.vllmApiKey="key1,key2,..."
Why do you need this feature?
From the vllm serve docs I'd expect that it's possible to set servingEngineSpec.vllmApiKey to a comma separated list of API keys. This would allow us to distribute multiple tokens to various stakeholder groups.
Additional context
The current behavior is that while comma separated strings do work but any tokens after the first one are discarded.
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 the Helm chart values and templates that feed servingEngineSpec.vllmApiKey and routerSpec.vllmApiKey, then compare the rendered arguments with vLLM's serve API-key behavior. Done means comma-separated values preserve every key for both configuration paths and the rendered deployment passes them through correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100