-
Notifications
You must be signed in to change notification settings - Fork 157
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
How to route /docs path in litserve behind a proxy? #352
Comments
hi @Mayurji, LitServe only exposes the endpoints which can be put behind a reverse proxy. It doesn't interfere with proxy directly, you might have to check the proxy that you are using on how to do this. |
@aniketmaurya , We have seen similar issues happening with Fastapi, which is also the backend for litserve. But it seems like, in fastapi they are able to update the root_path as mentioned in the below url. Can we update root_path for litserve as well. |
All the APIs by default starts with root path "/", are you able to set that to your proxy? |
@aniketmaurya , We cannot keep the root_path as proxy, we have multiple models under a common domains with different prefix. For different models, '/predict' works while '/docs' doesn't: https://domainName/modelV1/predict https://domainName/modelV2/predict |
hi @Mayurji, |
A somewhat similar issue: #270 |
I have hosted litserve as kubernetes(EKS) deployment with a service, now it is further connected to a proxy with Virtual service CRD and gateway.
In eks deployment,
Model: the url works 0.0.0.0:4000/predict after port forwarding.
Docs: The url works 0.0.0.0:4000/docs after port forwarding.
In EKS Service, the above url works, mapping 4000:4000, and then port forwarding.
Now, Istio's virtual service has prefix set as "modV1" and I am able to hit the model api as
domain-name/modV1/predict
But /docs api doesn't work from virtual service,
domain-name/modV1/docs
How to update or direct the /docs route in litserve for proxy?
The text was updated successfully, but these errors were encountered: