Prerequisites
Before deploying Conncentric, make sure the following tools and infrastructure are in place.
Bring Your Own Infrastructure
Conncentric follows a Bring Your Own Infrastructure (BYOI) model. You are responsible for provisioning and managing all underlying infrastructure. The platform boundary begins at the Helm chart: you provide a running Kubernetes cluster and a reachable PostgreSQL database; Conncentric runs inside it.
We do not provide Terraform modules, CloudFormation templates, or any other IaC scripts for your environment. Use your organization's own internal, compliance-approved provisioning tools and processes to set up the resources listed below. This ensures your deployment meets your security, networking, and compliance requirements from day one.
For a comprehensive pre-deployment walkthrough including network port approvals, infrastructure sizing baselines, and InfoSec FAQ, see the Day 0 Onboarding Runbook.
Tools You Need
| Tool | Minimum Version | What It's For |
|---|---|---|
| kubectl | 1.32+ | Managing your Kubernetes cluster from the command line |
| Helm | 4.1+ | Installing and upgrading Conncentric |
Infrastructure You Need
Kubernetes
You must provide a running Kubernetes cluster. Conncentric is compatible with any conformant distribution: EKS, GKE, AKS, or upstream Kubernetes.
Minimum cluster size:
| Resource | Minimum |
|---|---|
| Nodes | 2 |
| CPU per node | 2 cores |
| Memory per node | 4 GB |
| Kubernetes version | 1.30+ |
Provision this cluster using your organization's standard IaC tooling (Terraform, Pulumi, CloudFormation, or equivalent). Conncentric has no opinion on how the cluster is created, only that it meets the specifications above.
PostgreSQL
Conncentric stores all its configuration and state in a PostgreSQL database. You need to provision this before installing.
| Requirement | Details |
|---|---|
| Version | 15 or newer |
| Database | One dedicated database (e.g. conncentric) |
| User | A dedicated account with permission to create tables in that database |
| Storage | 20 GB minimum (more if you need long event log history) |
Use a managed database service (Amazon RDS, Google Cloud SQL, Azure Database for PostgreSQL) or a self-hosted instance, whichever aligns with your organization's policies. The platform sets up its own database tables automatically on first start. You do not need to run any SQL scripts manually.
Additional Infrastructure
Some plugins require additional infrastructure such as message brokers (e.g., Kafka). If your deployment uses these plugins, provision the required brokers through your own IaC processes. See the Official Plugins documentation for plugin-specific prerequisites.
Network Access
Adapter pods need outbound access to the external systems they connect to. The specific ports depend on the protocol and counterparty. Check with your external system's connectivity team.
Support Boundary
Connamara supports the Conncentric platform software running inside your cluster. Infrastructure provisioning, networking, IAM policies, and compliance controls for the underlying cloud environment are your responsibility. If you encounter issues during installation, our support team can help diagnose whether a problem originates in the platform or in the underlying infrastructure.
Helm Chart
The Conncentric Helm chart is at deployment/charts/conncentric in this repository. Use it directly:
helm install conncentric ./deployment/charts/conncentric -n conncentric -f my-values.yaml
If your deployment receives chart packages from Connamara directly, your representative will provide the chart archive and version to use.