Overview
LlamaCloud requires a few external dependencies — Postgres, MongoDB, Redis, and RabbitMQ.
Requirements
Section titled “Requirements”We officially support the following versions of the dependencies:
- Postgres
- Minimum Version
>=15.x - Admin Access to the database. LlamaCloud will read/write and apply migrations.
- We recommend
1 - 2 vCPUsand1 - 2 GBi RAMas a starting point for the database. As your usage grows, you can scale the database accordingly. - Recommended Managed Services:
- Minimum Version
- MongoDB
- Minimum Version
>=7.x - We recommend
1 - 2 vCPUsand1 - 2 GBi RAMas a starting point for the database. As your usage grows, you can scale the database accordingly. - Recommended Managed Services:
- Minimum Version
- RabbitMQ
- Minimum Version
>=3.11.x - We recommend
200 - 500m vCPUsand500Mi - 2GBi RAMas a starting point for the database. As your usage grows, you can scale the database accordingly. - Recommended Managed Services:
- Minimum Version
- Redis
- Minimum Version
>=7.x - We recommend
200 - 500m vCPUsand500Mi - 2GBi RAMas a starting point for the database. As your usage grows, you can scale the database accordingly. - Recommended Managed Services:
- Minimum Version
External Dependency Configuration (Recommended)
Section titled “External Dependency Configuration (Recommended)”To connect your LlamaCloud deployment to an external dependency, configure the necessary sections in your values.yaml file. Be sure to disable the subchart dependency as well. Otherwise, the external dependency configuration will be ignored.
For the most current and complete configuration examples, see our external dependencies example in the Helm repository.
global: config: postgresql: external: enabled: true host: <host> port: <port> database: <database> username: <username> password: <password> # the above values can also be set in a secret object # existingSecretName: <secret-name> # # Environment variables keys: # DATABASE_HOST, DATABASE_PORT, DATABASE_NAME, DATABASE_USER, DATABASE_PASSWORD # # Other optional environment variables: # DATABASE_POOL_TIMEOUT, DATABASE_POOL_RECYCLE, DATABASE_SSL_MODE, DB_CONNECTION_POOL_SIZE, DB_CONNECTION_POOL_MAX_OVERFLOW
# To disable the postgres subchart, set the following:postgresql: enabled: falseglobal: config: mongodb: external: enabled: true # The helm chart will construct the MONGODB_URL environment variable from the following values: scheme: "mongodb" host: <host> port: <port> username: <username> password: <password> # the above values can also be set in a secret object # existingSecretName: <secret-name> # # Environment variables keys: # MONGODB_URL (scheme://username:password@host:port) # or # MONGODB_URL_SCHEME, MONGODB_HOST, MONGODB_PORT, MONGODB_USER, MONGODB_PASSWORD
# To disable the mongodb subchart, set the following:mongodb: enabled: falseglobal: config: rabbitmq: external: enabled: true # The helm chart will construct the JOB_QUEUE_ENDPOINT environment variable from scheme, host, and port scheme: "amqp" host: <host> port: <port> username: <username> password: <password> # the above values can also be set in a secret object # existingSecretName: <secret-name> # # Environment variables keys: # JOB_QUEUE_ENDPOINT, JOB_QUEUE_USERNAME, JOB_QUEUE_PASSWORD
# To disable the rabbitmq subchart, set the following:rabbitmq: enabled: false:::tip Using Azure Service Bus
Prefer Azure Service Bus instead of RabbitMQ? Use the connection string option by setting global.config.rabbitmq.external.connectionString and disabling the RabbitMQ subchart. The Service Bus connection string should have Manage, Send, and Listen permissions. Requires Azure Service Bus Standard tier or higher (Basic is not supported). See the guide: Azure Service Bus as Job Queue.
:::
global: config: redis: external: enabled: true scheme: <scheme> # redis or rediss (for SSL) host: <host> port: <port> username: <username> # Note: this may be an optional field password: <password> db: 0 # default is 0 in the values.yaml
# the above values can also be set in a secret object # existingSecretName: <secret-name> # # Environment variables keys: # REDIS_HOST, REDIS_PORT, REDIS_PASSWORD, REDIS_SCHEME, REDIS_USERNAME (optional), REDIS_DB (optional) # or # REDIS_URL
# To disable the redis subchart, set the following:redis: enabled: falseComplete Configuration Reference
Section titled “Complete Configuration Reference”For the most up-to-date and comprehensive configuration options, refer directly to our Helm repository:
- Complete values.yaml reference - Full configuration options with detailed comments
- External dependencies example - Complete working example for external dependencies
- Helm chart documentation - Generated documentation with all configuration parameters
Subchart Configuration
Section titled “Subchart Configuration”As a default, the LlamaCloud Helm Chart will deploy subcharts for the dependencies listed above. Please refer to the following pages for more information on the subchart configuration: