Kubernetes
External PostgreSQL
Run Relic from the chart against a PostgreSQL database you already operate.
- Create a database and a user that owns it. Relic is tested on PostgreSQL 18 and applies its migrations at startup.
- Create the
relicnamespace:kubectl create namespace relic
Create a Secret with the database URL, admin password and encryption key:kubectl -n relic create secret generic relic \ --from-literal=databaseURL='postgres://relic:<password>@<db-host>:5432/relic?sslmode=require' \ --from-literal=adminPassword='<admin-password>' \ --from-literal=encryptionKey="$(openssl rand -base64 32)" - Put these settings in
values.yaml:cluster: enabled: false cloudnative-pg: enabled: false existingCredentialsSecret: relic - Install Relic:
helm install relic oci://ghcr.io/relicbuild/charts/relic --version 0.2.0-beta.4 -n relic -f values.yaml
SeaweedFS stays on. To replace it too, add the values from
External object storage
and put the S3 keys in the same Secret. Without existingCredentialsSecret,
set credentials.* instead.
Production database
- Take point-in-time-recovery backups, and keep
encryptionKeyapart from them (Secrets at rest). - Use
sslmode=requireor stricter. - Allow enough connections for every server and worker pod.