Helm chart API RAG

[samuelfernandof]

Hi Danny Ávila,

First of all, congratulations on your amazing work with Librechat! It’s an excellent project, very well-structured, actively maintained, and extremely useful for anyone building advanced AI systems!

I’ve been exploring the deployment options and noticed that LibreChat has a Helm chart for the main application and also one for the RAG API. From what I understood, in the LibreChat Helm chart, the RAG API is included as a dependency, correct?

In my case, I want to deploy LibreChat on my EKS cluster using Helm. However, I only found a chart version that integrates MongoDB. Is there currently any Helm chart available for deploying the RAG API with PostgreSQL and pgvector? Or do you recommend another approach to deploy your default pgvector-based setup on EKS?

Thanks in advance for your help, and again, congrats on the excellent project!

Best regards,
Samuel

[huttotw]

Unfortunately this is a side effect of the current helm setup. Helm does not recursively fetch the dependencies of nested dependencies during helm dependency update. Since we are including librechat-rag-api with file:// it does not resolve the postgresql dependency.

Instead, if we were to enable a proper repository helm repository using Github Pages (or otherwise) when we run helm dependency update it would pull librechat-rag-api from the helm repo and it's archive (.tgz) which includes all dependencies.

@iamNoah1 @hofq what do you think about using a traditional helm setup so that users can pull charts directly from the repo using Helm and adjacent tools?

[huttotw]

Better yet, I think the simplest thing to do is just have one helm chart and conditionally render the rag-api resources. I don't see a real reason for maintaining two separate helm charts at this stage.

[hofq]

my chart is built for a github pages repo as you can see in here

we should do the same thing here too.

I disagree with merging the charts, as it would make it confusing to read and understand. helm is a simple tool, i would like to not abstract deployments more than needed.

[hofq]

@danny-avila can you check if some permissions are missing in the repo settings? The Pipeline looks the same as in our old repo so it should release fine

[hofq]

I think there are some pipeline issues with github pages currently.

You should be able to use this one for now and only bump the tag, as it does not derivate much right now:

https://github.com/bat-bs/helm-charts/tree/main/charts/librechat

[huttotw]

@danny-avila could you help us out here? It seems like it might be a repo settings issue.

[danny-avila]

Would like to help, but not sure what the action is for me.

[huttotw]

@danny-avila I think we need to take the following steps:

1. Ensure Github Pages hosting is enabled for the repo for the branch gh-pages.
2. Use this action to publish updates to the helm chart, replacing the contents in .github/workflows/helmcharts.yml
3. And lastly, we should change the librechat helm chart to use the packaged version of librechat-rag-api in helm/librechat/Chart.yaml.

@hofq we could also change the directory the charts are in to be charts if we really wanted to follow Helm's standard pattern.

[hofq]

if you check the actions folder both here and in bat bs you will see there is no other step needed than one.

So @danny-avila would be nice if you could verify gh actions working here. Than we change the docs and it works.

The pre packaged stuff is not needed, as i stated above. There is an action that builds sub deps before building the main chart.

[danny-avila]

the gh-pages branch hasn't been updated since last year.

This is setup and not working since that branch likely needs updating:

Not sure if this is relevant:

#7782