Vouch request: Helm chart support for multi-region deployments #4288

Why do you want to contribute?

Hi Trigger team,

We are evaluating a multi-region self-hosted deployment model where the webapp runs in one primary region, while supervisors run in multiple regions close to workers/infrastructure.

Today the Helm chart supports this pattern for some dependencies, for example electric.deploy=false plus electric.external.url, but webapp and supervisor are always rendered together.

I’d like to contribute a Helm chart improvement for multi-region self-hosted deployments by adding optional deployment flags for those core components

Proposed shape:

webapp:
  deploy: true
  external:
    url: ""
    workerToken: ""
    existingSecret: ""
    existingSecretWorkerTokenKey: ""

supervisor:
  deploy: true

Use case:

• Primary region: webapp.deploy=true, supervisor.deploy=true
• Secondary regions: webapp.deploy=false, supervisor.deploy=true
• Secondary supervisors use webapp.external.url
• Worker token is provided through an existing secret rather than generated by the webapp token-syncer

The default values would remain unchanged, so normal single-region installs keep rendering both components.

Prior contributions or relevant experience

I’m a DevOps engineer working with Kubernetes, Helm, and AWS infrastructure, including multi-region service deployments. I’m currently integrating Trigger’s Helm chart into a Kubernetes environment with external Postgres/Aurora, Redis/ElastiCache, object storage, and region-specific supervisor placement.

This contribution comes from that integration work and would add backward-compatible support for split webapp/supervisor deployments in the Helm chart.