-
Notifications
You must be signed in to change notification settings - Fork 350
[Bugfix/Feature] Support extraPorts in service-vllm #725
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Signed-off-by: nargit <NargiT@users.noreply.github.com>
Summary of ChangesHello @NargiT, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request finalizes the support for defining and exposing Highlights
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR fixes incomplete implementation of extraPorts support in the service-vllm Helm chart. The feature allows adding additional ports to the VLLM service, which is useful for integrations like Istio sidecar metrics.
- Adds
extraPortsconfiguration to the values.yaml template with Istio example - Defines JSON schema validation for the
extraPortsarray structure - Integrates
extraPortsinto the service-vllm.yaml template and fixes helper template formatting
Reviewed Changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| helm/values.yaml | Adds commented example configuration for extraPorts with Istio sidecar metrics |
| helm/values.schema.json | Defines comprehensive JSON schema validation for extraPorts array with port specifications |
| helm/templates/service-vllm.yaml | Integrates extraPorts helper template into the service specification |
| helm/templates/_helpers.tpl | Fixes YAML indentation in the extraPorts helper template |
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code Review
This pull request adds support for extraPorts in the service-vllm Helm chart, allowing users to expose additional ports from the serving engine. The changes include updating the service template, adding a helper for the extra ports, defining the schema in values.schema.json, and providing an example in values.yaml. The implementation is solid, but I found a minor typo in the example provided in values.yaml which could cause issues for users if they copy it.
|
/gemini review |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code Review
This pull request aims to add support for extraPorts in the service-vllm service, which is a useful feature for integrations like Istio. The changes span across the Helm templates, values schema, and default values. While the overall approach is sound, there's a critical issue in helm/templates/service-vllm.yaml where the current implementation can produce invalid YAML if extraPorts is not defined. I've provided a suggestion to fix this by conditionally including the ports. The other changes, including the schema definition and the example in values.yaml, are well-implemented.
Signed-off-by: nargit <NargiT@users.noreply.github.com>
Signed-off-by: nargit <NargiT@users.noreply.github.com>
…ion-stack into bugfix/extraPorts
zerofishnoodles
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
* Support extraPorts in service-vllm Signed-off-by: nargit <NargiT@users.noreply.github.com> * fix typo Signed-off-by: nargit <NargiT@users.noreply.github.com> * Enable extra ports for router Signed-off-by: nargit <NargiT@users.noreply.github.com> * fix extraPorts indentation Signed-off-by: nargit <NargiT@users.noreply.github.com> --------- Signed-off-by: nargit <NargiT@users.noreply.github.com> Co-authored-by: nargit <NargiT@users.noreply.github.com> Co-authored-by: Rui Zhang <51696593+zerofishnoodles@users.noreply.github.com> Signed-off-by: senne.mennes@capgemini.com <senne.mennes@capgemini.com>
Useful for istio.
-swhen doinggit commit[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 thevllm_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:
pre-committo format your code. SeeREADME.mdfor installation.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
-swithgit commitwill automatically add this header.What to Expect for the Reviews
We aim to address all PRs in a timely manner. If no one reviews your PR within 5 days, please @-mention one of YuhanLiu11
, Shaoting-Feng or ApostaC.