Skip to content

Kubernetes: what you need

RAG Platform 1.1 ships no Kubernetes manifests or Helm chart yet. If you run it on your own cluster, rebuild what docker-compose.yml of rag-docker 1.1.0 describes. This page lists what that takes.

Workloads

Workload Image (registry.git.nrw/ki-expertisezentrum.nrw/apps/rag/…) Kind Notes
web-gateway rag-web/web-gateway:1.1.0 Deployment Listens on port 8080. The only service to expose (Ingress or LoadBalancer)
web-gateway-migrations rag-web/web-gateway-migrations:1.1.0 Job Run to completion before web-gateway starts, on every upgrade
api-gateway rag-system/api-gateway:1.1.0 Deployment Listens on port 8000, internal only. RAG Web reaches it through FilesOptions__Endpoint
ingestion rag-system/ingestion:1.1.0 Deployment No port
dlq-consumer rag-system/dlq-consumer:1.1.0 Deployment No port
rag-database-migrations rag-system/migrations:1.1.0 Job Run to completion before the RAG System services start, on every upgrade

Use the image digests from Versioning and compatibility to pin exactly the released images.

Dependencies

Dependency Requirement
RAG database PostgreSQL with pgvector and pg_search. Use the rag-system/postgres:1.1.0 image, or provide the same extensions
Gateway database Plain PostgreSQL (the compose file uses postgres:18.1)
Message broker RabbitMQ (compose: rabbitmq:4.4.0)
Cache Valkey (compose: valkey/valkey:9.0.7)
Inference provider OpenAI-compatible endpoints for embeddings (4096 dimensions), generation and chat

Storage

  • api-gateway, ingestion and dlq-consumer share a folder for uploaded files, mounted at TEMP_UPLOAD_DIR (default /app/temp_data). On Kubernetes, that means a ReadWriteMany volume mounted into all three, or running them on one node.
  • Persistent volumes for both databases and for RabbitMQ.

Configuration

  • Provide the variables from Configuration as a ConfigMap and Secrets. Kubernetes doesn't expand ${…}, so write connection strings with literal values, and replace the compose service names (gateway-database, valkey, api-gateway, rag-database, rabbitmq) with your Service names.
  • Set APP_RELEASE=1.1.0 on web-gateway, api-gateway, ingestion and dlq-consumer, so that GET /version reports the product release.
  • Create tenants and API keys in the gateway database as described in Tenants and API keys.

Probes

GET /version on web-gateway (port 8080) needs no API key and can serve as a liveness check.