Connect with a Password
Use a password for any PostgreSQL that cannot sign in with a cloud identity, such as a self-managed server. The application and the migration Job read the same URL from one Kubernetes Secret.
Store the URL in a Secret
-
In the Helm release namespace (
archestrain the installation example), create a Kubernetes Secret namedarchestra-databasewith the complete connection URL in itsurlkey. -
Reference it in the shared application settings:
yamlpostgresql: enabled: false archestra: envWithValueFrom: - name: ARCHESTRA_DATABASE_URL valueFrom: secretKeyRef: name: archestra-database key: urlThe migration Job inherits this Secret reference. The chart runs migrations before rolling out an upgrade. Keep
archestra.migrationJob.enabledenabled unless your pipeline applies migrations separately. -
Apply the Helm upgrade and confirm the migration Job succeeds before checking the application rollout.
Verify TLS Certificates
To verify the database server certificate, mount your CA bundle in every database client and include ?sslmode=verify-full&sslrootcert=/etc/ssl/db/ca.pem in the database URL:
archestra:
extraVolumes:
- name: db-ca
secret:
secretName: db-ca-bundle
extraVolumeMounts:
- name: db-ca
mountPath: /etc/ssl/db
readOnly: true
The chart applies these mounts to web pods, worker pods, and the migration Job. Use a Secret or ConfigMap for the CA; the migration Job skips persistent-volume claims.