Repository navigation
Replies: 3 comments
|
We'd definitely be open to accepting PRs around this! |
0 replies
|
Strong +1 for Helm charts! Kubernetes deployment is essential for production RAG. What a good R2R Helm chart should include:
Quick workaround until official chart: # Convert docker-compose to k8s manifests
kompose convert -f docker-compose.yml
kubectl apply -f .We deploy RAG systems on K8s at Revolution AI — happy to contribute to a Helm chart if maintainers are interested! |
0 replies
|
+1 for Helm chart! Kubernetes-native deployment is essential for production. Basic Helm structure for R2R: Key values.yaml: replicaCount: 2
image:
repository: sciphi/r2r
tag: latest
resources:
requests:
memory: "2Gi"
cpu: "1"
limits:
memory: "4Gi"
cpu: "2"
autoscaling:
enabled: true
minReplicas: 2
maxReplicas: 10
targetCPUUtilization: 70
vectordb:
type: qdrant # or pgvector
external: true
host: qdrant.default.svcHPA for autoscaling: apiVersion: autoscaling/v2
kind: HorizontalPodAutoscaler
metadata:
name: r2r
spec:
scaleTargetRef:
apiVersion: apps/v1
kind: Deployment
name: r2r
minReplicas: 2
maxReplicas: 10
metrics:
- type: Resource
resource:
name: cpu
target:
type: Utilization
averageUtilization: 70We deploy R2R on Kubernetes at Revolution AI — would love to contribute to an official Helm chart! |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hey! You’ve got a Docker Compose YAML, which is great, but it would be awesome to have a Helm chart as well. Right now, there’s no easy way to deploy R2R in a Kubernetes cluster, and it would be really helpful if Kubernetes itself could handle scaling the resources for R2R.
All reactions