_Docs/
Get StartedModulesPlatformDeployCookbookChangelogReference
_Deploy
  • Deployment Overview
    • Overview
    • Requirements
    • Demo
      • All-in-one Demo Chart
    • Installation
      • Operator Setup
      • Control Plane SetupEE
    • Infrastructure Services
      • PostgreSQL
      • Message Broker
      • Temporal
    • Module Configuration
      • Stack Configuration
      • Gateway Module
      • Ledger Module
      • Payments Module
      • Auth ModuleEE
      • Orchestration ModuleEE
      • Reconciliation ModuleEE
      • Wallets ModuleEE
      • Webhooks ModuleEE
    • Configuration Reference
      • Operator settings reference
      • API Reference
    • Backups management
    • Troubleshooting
    • Configure OpenTelemetry
    • Traces
    • Metrics
    • Upgrade from the operator
    • Database update
  1. Deploy
  3. Self-Hosted
  5. Module Configuration
  7. Stack Configuration
Deploy

Stack Configuration

This page requires self-hosted edition.
Deployment

Overview#

A Stack represents a set of modules that are deployed together. It is used as a way to group modules and to deploy them together with a consistent set of versions and configurations.

When you deploy a Formance module, such as Ledger or Payments, you deploy them within a Stack. This allows you to ensure that they are all deployed with the same versions and configurations.

Stack Object#

The first object that needs to be created is the Stack object. This allows linking the different modules and deploying them together.

You can find all the available parameters in the comprehensive CRD documentation.

YAML
apiVersion: formance.com/v1beta1
kind: Stack
metadata:
  name: formance-dev
spec:
  versionsFromFile: v2.0

During the deployment of the Operator and for its future upgrades, the Versions files are automatically updated following the semver pattern. It is possible to specify a specific version by using the versionFromFile field in the Stack file.

TemporalGateway Module
On This Page
  • Overview
  • Stack Object