Deploy and operate DALP: plan, install, and run an instance

A DALP Instance deploys the Platform API, Console, and supporting services into Kubernetes. These pages cover topology, prerequisites, installation, monitoring, upgrades, and recovery. Start with topology for a new deployment, runbooks for an incident, or Upgrades and migrations for a release window.

Plan the shape first

Three comparisons come before any chart runs, because the install asks you to commit to their answers.

Topologies

Every dalp release runs the Platform API as three separately scaled roles: api, runner, indexer. Compare each role's replica range, what growth costs at PgBouncer, and which chart bundle fits your environment.

Hosting and access

Whose infrastructure the instance runs on, and how much of it the vendor can reach, are two separate decisions. The ladder runs from operator access to the cluster down to a mirrored registry for installations that cannot pull vendor images directly.

Security and compliance posture

The control layers a reviewer checks before accepting an instance: who can sign in versus who can move assets, custody separated from compliance, and what stays visible on chain.

Prepare what it connects to

Confirm every endpoint, credential, and unit of capacity the instance needs, and decide which of them the support chart bundles for you and which you supply yourself, before you install.

Networks

Declare the ledger networks the instance settles assets on. Each entry defines a built-in EVM alias or a custom EVM chain, and the instance validates the whole list before it serves traffic.

Prerequisites

The external endpoints, credentials, and cluster capacity a DALP installation needs ready before you run the charts, and which of them the support chart bundles for you instead.

Install, connect, and keep it current

Install runs the charts in the order that avoids a failed first install. Once the instance is running, connect an external identity provider and point telemetry at your own collector or the bundled stack, both through a values change that needs no reinstall. Every later version then moves through one helm upgrade that treats the whole release as one unit.

Install

Up to three charts and one cluster-level bundle of Custom Resource Definitions (CRDs), the Kubernetes objects that teach the cluster new resource kinds. Installing them is not optional: apply the Gateway API CRDs before any release that renders an HTTPRoute, or that release fails at install time on the unknown resource kind.

SSO

Connect an external identity provider over OpenID Connect (OIDC), the standard behind single sign-on (SSO), and know what the switch throws: one complete provider entry replaces local sign-in, email, password, and passkey, for every user on the deployment.

Observability

Metrics and logs leave the pod over the OpenTelemetry Protocol (OTLP) unsampled; traces export at a configured sample fraction, 10% by default. Point the export at your own collector, or at the bundled in-cluster stack.

Upgrades and migrations

One helm upgrade moves every component together, with a database migration Job that gates rollout when the default pre-upgrade hook is used, and that stays in place for inspection when it fails.

Recover with a proven path back

Backup and disaster recovery

In-cluster backup with Velero is an optional capability configured through the dalp or support chart, not a default. See what it covers, what your managed PostgreSQL, Redis, and object storage must back up themselves, and how to prove a backup actually restores.

Runbooks

Start from the symptom: a pod that stays out of Ready, indexed chain data that stops advancing, or webhook deliveries that stop arriving.

When the vendor runs the infrastructure for you, the install and upgrade pages describe work that happens on your behalf, while the plan and integrate pages still describe the instance you sign in to. Check SettleMint status for published availability on SettleMint-hosted environments, and read the SettleMint Trust Center for the security and compliance documentation a security review or audit asks for.

Deploy and operate DALP

Plan the shape firstCopy Anchor Link