[Feat] add vllm-api-key

[JustinDuy]

FIX #150

BEFORE SUBMITTING, PLEASE READ THE CHECKLIST BELOW AND FILL IN THE DESCRIPTION ABOVE

---

• Make sure the code changes pass the pre-commit checks.
• Sign-off your commit by using -s when doing git commit
• Try to classify PRs for easy understanding of the type of changes, such as [Bugfix], [Feat], and [CI].

Detailed Checklist (Click to Expand)

Thank you for your contribution to production-stack! Before submitting the pull request, please ensure the PR meets the following criteria. This helps us maintain the code quality and improve the efficiency of the review process.

PR Title and Classification

Please try to classify PRs for easy understanding of the type of changes. The PR title is prefixed appropriately to indicate the type of change. Please use one of the following:

• [Bugfix] for bug fixes.
• [CI/Build] for build or continuous integration improvements.
• [Doc] for documentation fixes and improvements.
• [Feat] for new features in the cluster (e.g., autoscaling, disaggregated prefill, etc.).
• [Router] for changes to the vllm_router (e.g., routing algorithm, router observability, etc.).
• [Misc] for PRs that do not fit the above categories. Please use this sparingly.

Note: If the PR spans more than one category, please include all relevant prefixes.

Code Quality

The PR need to meet the following code quality standards:

• Pass all linter checks. Please use pre-commit to format your code. See README.md for installation.
• The code need to be well-documented to ensure future contributors can easily understand the code.
• Please include sufficient tests to ensure the change is stay correct and robust. This includes both unit tests and integration tests.

DCO and Signed-off-by

When contributing changes to this project, you must agree to the DCO. Commits must include a Signed-off-by: header which certifies agreement with the terms of the DCO.

Using -s with git commit will automatically add this header.

What to Expect for the Reviews

Could you please review this @YuhanLiu11 , @ggaaooppeenngg ?

[YuhanLiu11]

Hi @JustinDuy thanks for your contribution! Can you fix the DCO issue? (when committing, add -s in git commit).

Thanks a lot!

[ApostaC]

@JustinDuy Thanks for contributing and it's great that you added functionality tests as well.

Seems that .github/values-05-secure-vllm.yaml is missing in this PR, can you also quickly fix it to make the functionality test pass?

[JustinDuy]

@JustinDuy Thanks for contributing and it's great that you added functionality tests as well.

Seems that .github/values-05-secure-vllm.yaml is missing in this PR, can you also quickly fix it to make the functionality test pass?

[JustinDuy]

@YuhanLiu11 , @ApostaC : i closed the PR by accident. Is it possible to re-open it?

[kinoute]

Great addition!

[JustinDuy]

@YuhanLiu11 , @ApostaC , @Shaoting-Feng , @gaocegege : Could anyone trigger the test and review please?

[ApostaC]

Otherwise LGTM!

[ApostaC]

Can you change the file name since there are multiple new tutorials added recently. Thanks!

[JustinDuy]

@ApostaC : Thank you! 've renamed the tutorial files. It's great to see the project advancing fast!

[JustinDuy]

@ApostaC : Could you please trigger the tests and merge if everything is ok?

[JustinDuy]

@ApostaC : One more time please!

[YuhanLiu11]

@JustinDuy just started running the tests!

[JustinDuy]

@YuhanLiu11, @ApostaC : Could you please trigger again? I increased the time-out. Look like we have this timeout error once in a while. Maybe timeout 2 mins should be increased also for the other helm tests...

[YuhanLiu11]

@JustinDuy tests passed! I'll merge it now.

[YuhanLiu11]

@JustinDuy seems to be some issues with the new test you added. 😢 Could you fix it when you get a chance? Thanks for your contribution!

[YuhanLiu11]

LGTM! Thanks!