Installation process
Overview of the SettleMint-managed installation process for self-hosted DALP deployments. Covers pre-installation verification, deployment phases, and post-installation handoff.
Overview
This page explains the installation process and outcomes without listing commands. SettleMint performs the deployment while your team provides infrastructure access and prerequisites.
The post-Kubernetes setup stage is always performed by SettleMint and requires access to the target environment.
What SettleMint delivers
| Deliverable | Description |
|---|---|
| Helm chart package | Versioned charts for DALP and supporting components |
| Image registry credentials | Harbor credentials for harbor.settlemint.com |
| Baseline configuration | Deployment-ready defaults aligned with your environment |
| Deployment plan | Verified install sequence and validation checklist |
What clients provide
| Requirement | Description |
|---|---|
| Kubernetes or OpenShift access | kubeconfig with permissions to install charts and CRDs |
| Prerequisites | All items from the prerequisites checklist |
| Environment values | Domains, certificates, and managed service credentials |
| Change window | Time window for deployment and verification |
| Post-setup access | Network access for contract, and subgraph tasks |
Installation stages
Stage 1: Pre-installation verification
Purpose: confirm that infrastructure, services, and network access match the prerequisites.
- Validate cluster access, namespaces, and storage classes
- Verify managed service connectivity (PostgreSQL, Redis, object storage)
- Confirm DNS and TLS readiness for enabled routes
- Review CRD approvals and security constraints (SCCs on OpenShift)
Stage 2: Platform deployment
Purpose: install the Helm charts and bring all DALP services online.
- Install operators and supporting charts in the required order
- Deploy DALP services and networking (Ingress on Kubernetes, Routes on OpenShift)
- Apply default labels, annotations, and security settings
Result: all core services are running and reachable inside the cluster.
Stage 3: Post-deployment setup (SettleMint-owned)
Purpose: connect on-chain assets, validate chain indexing, and finalize application configuration.
- Deploy smart contracts and record addresses
- Validate DIDX connectivity and sync health
- Update application configuration with contract and endpoint references
Result: the platform is fully wired to the blockchain network and ready for use.
Stage 4: Verification and handoff
Purpose: confirm health, security, and operational readiness before client handoff.
- Validate ingress routes, TLS, and authentication
- Confirm dashboards and alerts are producing data
- Verify backup configuration and restore readiness
Result: you receive a working platform with verified endpoints and access details.
If the client must run the platform deployment
SettleMint can support client-led deployment in exceptional cases, but the post-deployment setup remains SettleMint-owned.
Required tooling and access
- Helm version 3.x and kubectl (or oc CLI on OpenShift) configured for the target cluster
- Ability to install CRDs, IngressClass (or Routes on OpenShift), and namespace-scoped resources
- Harbor credentials and egress access to harbor.settlemint.com
- Access to managed service credentials and TLS certificates
Required inputs
- Final FQDN list for enabled routes
- TLS certificates and private keys for each route
- PostgreSQL, Redis, and object storage connection details
- Approval for any operator CRDs required by the charts
Handoff package
You receive the following after installation:
- Application and API endpoint inventory
- Admin credentials for enabled services
- Deployed contract addresses and network references
- DIDX endpoint information and sync status
- Configuration reference for future upgrades
Post-installation support
Support response and incident handling depend on your contracted SLA tier. SettleMint provides upgrade guidance and remediation for DALP components within the agreed support scope.
Timeline expectations
| Phase | Typical duration |
|---|---|
| Pre-installation verification | 1 to 2 business days |
| Platform deployment | 1 to 2 business days |
| Post-deployment setup | 4 to 8 hours |
| Verification and handoff | 2 to 4 hours |
| Total | 2 to 4 business days |
Timelines assume prerequisites are complete. Gaps in infrastructure or approvals extend the schedule.
See also
- Prerequisites for infrastructure requirements
- High availability for HA and DR configurations
- DALP Execution Engine for component architecture
Prerequisites
Exhaustive checklist of infrastructure, services, and credentials required before SettleMint can begin DALP installation. Review and complete all requirements to prevent deployment delays.
OpenShift installation
OpenShift-specific deployment guidance for self-hosted DALP installations. Covers SCC requirements, Route configuration, and OpenShift Data Foundation integration for enterprise OpenShift environments.