Nesis Helm Chart
For your production deployment, use the provided helm chart. Save the overrides values file on your local.
Installing to Kubernetes
overrides.yml | |
---|---|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 |
|
Then add the helm repository with
1 2 |
|
Lastly, install Nesis into your kubernetes cluster with
1 |
|
Shortly after, you should see all services running as shown using kubectl get po
below
NAME READY STATUS RESTARTS AGE
nesis-api-664679c8f9-9vzhb 1/1 Running 0 45s
nesis-frontend-5f69fcb4d5-cpnd7 1/1 Running 0 45s
nesis-memcached-7d7855657d-zxd82 1/1 Running 0 45s
nesis-minio-6d458bc7-cpgql 1/1 Running 0 45s
nesis-postgresql-0 1/1 Running 0 45s
nesis-rag-757584f46c-9kqtf 1/1 Running 0 45s
RAG Configuration
- You need to set the
OPENAI_API_KEY
andOPENAI_API_BASE
environment variables before you can start chatting with your documents. - We noticed that some Huggingface embeddings models can only be used after authenticating with Huggingface. If you
encounter 401s during embeddings generation, you need to obtain a Huggingface token and populate the
HF_TOKEN
environment variable.
Testing your Nesis
-
Port forward services;
MinIO Frontendkubectl port-forward svc/nesis-minio 9001
-
Point your browser to http://localhost:9001 and login with
admin
:password
. -
In another terminal;
Nesis Frontendkubectl port-forward svc/nesis-frontend 8000
-
Point your browser to http://localhost:8000 and login with
test@domain.com
:password
. -
Upload documents into the MinIO bucket
private-documents
. - In the
Nesis Frontend
add a datasource with;- Navigate to Settings->Datasources.
- Click Add.
- Enter
- Type: MinIO (S3 Compatible)
- Name: ds-private-documents
- Entpoint: http://nesis-minio:9000
- User: admin
- Password: password
- Dataobjects: private-documents
- Click Save.
- In the datasource list, find the datasource you just created and click the Ingest button.
- View logs of your services using
kubetail
withkt nesis
- Once ingestion is complete, navigate to Documents and you can start chating with your documents.
Overriding Key Dependencies
The Nesis helm chart allows you to override the following components;
- Postgres database that backs the API component.
- Memcached caching service.
- Vector database
Resource requirements
- The Frontend and API microservices are lightweight and don't need alot of resources.
- The RAG Engine however needs to be scoped for enough memory, cpu and storage.
- The Postgres database needs enough memory and storage because every ingested document.