-
Notifications
You must be signed in to change notification settings - Fork 266
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
Ignore worker pods for gateway routing #776
Conversation
Signed-off-by: Varun Gupta <varungup90@gmail.com>
@@ -75,6 +75,7 @@ type Block struct { | |||
|
|||
const ( | |||
modelIdentifier = "model.aibrix.ai/name" | |||
nodeType = "ray.io/node-type" |
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.
I am thinking if we want to add a aibrix label like orchestration.aibrix.ai/server-pod
. autoscaling need that feature as well. We can start with ray specific label and replace with our own later as a separate issue
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.
Agree, we have implement correctly in next iteration.
Signed-off-by: Varun Gupta <varungup90@gmail.com>
Signed-off-by: Varun Gupta <varungup90@gmail.com>
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
* Ignore worker pods for gateway routing * ignore worker pods in UpdatePod as well * use node worker as const Signed-off-by: Varun Gupta <varungup90@gmail.com> Signed-off-by: Liguang Xie <liguang.vt@gmail.com>
* Ignore worker pods for gateway routing * ignore worker pods in UpdatePod as well * use node worker as const Signed-off-by: Varun Gupta <varungup90@gmail.com>
* Ignore worker pods for gateway routing * ignore worker pods in UpdatePod as well * use node worker as const Signed-off-by: Varun Gupta <varungup90@gmail.com>
* Ignore worker pods for gateway routing (#776) * Ignore worker pods for gateway routing * ignore worker pods in UpdatePod as well * use node worker as const Signed-off-by: Varun Gupta <varungup90@gmail.com> * Disable ENABLE_PROBES_INJECTION in correct way (#779) fix env error caused by helm set command, use —set-string for env bool Signed-off-by: Jiaxin Shan <seedjeffwan@gmail.com> * Make stream include usage as optional (#788) * Make stream include usage as optional --------- Signed-off-by: Varun Gupta <varungup90@gmail.com> * Append ray head label selector in PodAutoscaler (#789) It helps to only consider the engine pod for multi-node inference. Ray worker doesn’t have http server running and it can not expose any application but only resource metrics. For resource metrics, since we use Tensor Parallelism, we think the utilization across GPU are same. Signed-off-by: Jiaxin Shan <seedjeffwan@gmail.com> * Update request message processing for /v1/completion input (#794) Update request message processing for prompt input Signed-off-by: Varun Gupta <varungup90@gmail.com> * Fix a cherry-pick package name issue Signed-off-by: Jiaxin Shan <seedjeffwan@gmail.com> * Add missing release branch pull requests trigger Signed-off-by: Jiaxin Shan <seedjeffwan@gmail.com> --------- Signed-off-by: Varun Gupta <varungup90@gmail.com> Signed-off-by: Jiaxin Shan <seedjeffwan@gmail.com> Co-authored-by: Varun Gupta <varungup90@gmail.com>
* Ignore worker pods for gateway routing * ignore worker pods in UpdatePod as well * use node worker as const Signed-off-by: Varun Gupta <varungup90@gmail.com> Signed-off-by: Le Xu <le.xu@bytedance.com>
Pull Request Description
Ignores worker pods for gateway routing
Related Issues
Resolves: part of #758
Important: Before submitting, please complete the description above and review the checklist below.
Contribution Guidelines (Expand for Details)
We appreciate your contribution to aibrix! To ensure a smooth review process and maintain high code quality, please adhere to the following guidelines:
Pull Request Title Format
Your PR title should start with one of these prefixes to indicate the nature of the change:
[Bug]
: Corrections to existing functionality[CI]
: Changes to build process or CI pipeline[Docs]
: Updates or additions to documentation[API]
: Modifications to aibrix's API or interface[CLI]
: Changes or additions to the Command Line Interface[Misc]
: For changes not covered above (use sparingly)Note: For changes spanning multiple categories, use multiple prefixes in order of importance.
Submission Checklist
By submitting this PR, you confirm that you've read these guidelines and your changes align with the project's contribution standards.