-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
remove vllm-check/tgi-check init-container #1605
Conversation
Tested by injecting the changes directly to deployment manifest. |
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
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.
added one comment about using a list or arguments, but if tested and works fine then LGTM, thanks.
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
This change may cause issues if we ever want to introduce liveness\readiness probes to h2oGPT. |
^ +1, If the inference service is vLLM and if Model Lock is used the check will not be needed, it can be disabled completely |
thanks @ozahavi, would you elaborate more about moving wget into h2ogpt container would be an issue for liveness/readiness? |
like this: {{- if and .Values.vllm.enabled (not .Values.h2ogpt.externalLLM.enabled) }} |
Yes, and also you can stick with Model Lock itself for locally hosted LLMs and if the inference is vLLM the wget check is not needed (if you use Model Lock) |
like this: {{- if and .Values.vllm.enabled (not .Values.h2ogpt.externalLLM.modelLock) }} |
tested with:
|
Yup lgtm |
add wget vllm into h2ogpt container
fixing: #1603