feifeigood 30e1e546cf MUL-3355: feat(helm): support external PostgreSQL via postgres.external.enabled ...

Closes #4237

Add a `postgres.external.enabled` toggle (default: false) so operators
can skip the built-in Deployment/PVC/Service and point Multica at any
externally managed PostgreSQL (CNPG, RDS, Cloud SQL, Neon, etc.).

When enabled:
- postgres Deployment, PVC, and ClusterIP Service are not rendered
- The hard-coded DATABASE_URL env var is omitted from the backend pod;
  DATABASE_URL must be supplied in existingSecret and reaches the
  container through the existing envFrom.secretRef mechanism
- POSTGRES_DB / POSTGRES_USER are omitted from the ConfigMap (unused
  when DATABASE_URL is provided directly)

Also update the existingSecret creation example in values.yaml to show
both the built-in and external-postgres variants so users know to add
DATABASE_URL instead of POSTGRES_PASSWORD when switching modes.

Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>

2026-07-03 13:56:10 +08:00

..

templates

MUL-3355: feat(helm): support external PostgreSQL via postgres.external.enabled

2026-07-03 13:56:10 +08:00

Chart.yaml

…

values.yaml

MUL-3355: feat(helm): support external PostgreSQL via postgres.external.enabled

2026-07-03 13:56:10 +08:00