Skip to content
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

LLM rails not working on Kubernetes - Pod restarts with out any errors #752

Open
moka1602 opened this issue Sep 16, 2024 · 4 comments
Open
Assignees
Labels
status: needs info Issues that require more information from the reporter to proceed.

Comments

@moka1602
Copy link

Hi ,

I am using input guardrails for my chatbot which is working perfectly fine in local. The problem is starts deploying the fast API on kubernetes. As soon as we hit the api , the pod restarts at LLMRails(config=config, verbose=True) . No errors !!!
Using the vertexAI model for both LLM and embeddings. PLS HELP!!!

config.yaml

models:
- type: main
engine: vertexai
model: gemini-1.0-pro
- type: embeddings
engine: vertexai
model: text-embedding-004

core:
embedding_search_provider:
name: default
parameters:
embedding_engine: vertexai
embedding_model: text-embedding-004
cache:
enabled: False
key_generator: md5
store: in_memory
store_config: {}

knowledge_base:
embedding_search_provider:
name: default
parameters:
embedding_engine: vertexai
embedding_model: text-embedding-004
cache:
enabled: False
key_generator: md5
store: in_memory
store_config: {}

Image

@moka1602
Copy link
Author

Anyone tried deploying a chatbot with guardrails on Kubernetes faced this issue ? Pls suggest.

@drazvan

@Pouyanpi
Copy link
Collaborator

Hi @moka1602 , when you say that you are deploying FastAPI app, how are you doing it exactly? Are you using the Dockerfile in the repo to build the image? When you run the image would it work?

@Pouyanpi Pouyanpi self-assigned this Sep 17, 2024
@Pouyanpi Pouyanpi added the status: needs info Issues that require more information from the reporter to proceed. label Sep 17, 2024
@fedewj
Copy link

fedewj commented Nov 19, 2024

are there any updates? I'm facing a similar problem

@Pouyanpi
Copy link
Collaborator

@jingwangfe would you please open a new issue and refer to this issue there? We need more info to be able to reproduce this issue but currently we don't have much. Opening a new issue would make this easier for you and us.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: needs info Issues that require more information from the reporter to proceed.
Projects
None yet
Development

No branches or pull requests

3 participants