Database Configuration

Conncentric uses PostgreSQL to store everything: adapter configurations, artifacts, plugin files, and operational state. You provision the database before installing Conncentric, and the platform manages its own tables from there.

Setting Up the Database

Create a dedicated database and user:

CREATE USER conncentric WITH PASSWORD 'your-password';
CREATE DATABASE conncentric OWNER conncentric;
GRANT ALL PRIVILEGES ON DATABASE conncentric TO conncentric;

The account needs permission to create tables. On managed services like RDS, grant the user the rds_superuser role or equivalent.

Automatic Schema Setup

The platform creates and updates its own database tables automatically when it starts. You don't run any SQL scripts manually. Just point the Orchestrator at your database and start it. The same process runs on upgrades, applying only what has changed since the last version.

New database versions are designed to be backward-compatible with the previous release, so you can roll out upgrades one pod at a time without taking anything offline.

Helm Configuration

Database connection details are set under the shared database key at the root of your values file. Both the Orchestrator and Adapter read from this section.

database:
  host: "postgres.example.com"
  port: 5432
  name: "conncentric"
  auth:
    username: "conncentric"
    password: "your-password"

Using a Kubernetes Secret (Recommended for Production)

Don't put passwords directly in your values file. Reference a Kubernetes Secret instead:

database:
  host: "postgres.example.com"
  port: 5432
  name: "conncentric"
  auth:
    existingSecret: "conncentric-db-credentials"

Create the secret before deploying:

kubectl create secret generic conncentric-db-credentials \
  --from-literal=username=conncentric \
  --from-literal=password=your-password \
  -n conncentric

Managed Database Services

Conncentric works with all major managed PostgreSQL services:

Provider	Service
AWS	RDS for PostgreSQL, Aurora PostgreSQL
Google Cloud	Cloud SQL for PostgreSQL
Azure	Azure Database for PostgreSQL – Flexible Server

When using a managed service, make sure TLS is enabled and the Orchestrator pod can reach the database endpoint from inside your cluster.

Backup and Recovery

Conncentric doesn't manage database backups. Use your database provider's backup tools:

• RDS: Automated snapshots + point-in-time recovery
• Cloud SQL: Automated backups with configurable retention
• Self-managed: Regular pg_dump exports

All platform data (configurations, artifacts, plugins) lives in the database. A successful database restore is all you need to recover the platform.