Cannot scale my ledger deployment on stack version v3.0

[lior-lew]

Hello,
on the ticket, ttps://github.com/orgs/formancehq/discussions/1864 I was told to use Ledger v2.30-alpha. I tried it and I am getting imagePullError. so I tried the following:

spec: debug: false deploymentStrategy: single-writer dev: false stack: formance-stg version: v2.3.0 

and I am getting a single pod with no ability to scale the deployment.
my stack version is v3.0

Thank you,
Lior

[aalloiteau]

Hi,

Scaling behavior from v2.2 onward
Stack switches to a stateless model. Deployments are defined via .spec.deployments instead.

• The deploymentStrategy field stops being effective starting v2.2.
• The operator now uses explicit .spec.deployments configuration instead.
• Ledger and ledger-worker are treated as independent Kubernetes Deployments — no automatic writer/reader split anymore.

v2.3.0 and above:

• Adds a ledger-worker alongside the ledger.
• The ledger-worker handles background tasks (processing events, async jobs, etc.).
• single mode / single-writer is still the default, even if you don’t specify it. That’s why you’re seeing just 1 pod by default.

You can’t scale by default b/c, you must configure deployments.ledger.replicas and deployments.ledger-worker.replicas in your stack spec.

• The operator manages the stack, so directly scaling the pods via kubectl scale won’t persist; it will reset to the default defined in the stack spec.
• By default, replicas for ledger and ledger-worker are set to 1 (single pod) unless you explicitly configure them.

cc @Dav-14 please comment if I'm missing something

deployments: ledger: replicas: 3 ledger-worker: replicas: 2