feat: add PostgreSQL support for manager database

[bumarcell]

Summary

The Dragonfly manager application has supported PostgreSQL since dragonflyoss/dragonfly#1459, but the Helm chart only renders MySQL configuration. This adds PostgreSQL support to the chart.

Changes

values.yaml

• New externalPostgres section: enable, host, port, database, username, password, sslMode, timezone, migrate
• New manager.extraInitContainers: [] — generic escape hatch for additional init containers
• New manager.renderConfig: false — opt-in flag that swaps the /etc/dragonfly mount from the raw ConfigMap to an emptyDir, so a user-supplied init container can render the final manager.yaml (e.g. by substituting credentials pulled from a Kubernetes Secret)
• Commented-out example in the externalPostgres section showing how to combine renderConfig: true + an init container to inject credentials from a Secret

manager-configmap.yaml

• Adds database.type field (postgres when enabled, mysql otherwise)
• Renders database.postgres block when externalPostgres.enable is true
• mysql block only rendered when postgres is disabled

manager-deployment.yaml

• Adds manager.extraInitContainers support via common.tplvalues.render
• When manager.renderConfig is true, mounts a config-rendered emptyDir at /etc/dragonfly instead of the raw ConfigMap, and declares that emptyDir volume. The user's extraInitContainers entry is expected to read the raw ConfigMap (from an extraVolumeMounts path) and write the rendered manager.yaml to /etc/dragonfly/manager.yaml.
• Default (renderConfig: false): manager mounts the ConfigMap directly, extraInitContainers stays a pure escape hatch with no volume side effects — static credentials in values.yaml work out of the box for both externalPostgres and externalMysql.

Usage

Direct credentials

mysql:
  enable: false
externalPostgres:
  enable: true
  host: my-postgres-host
  username: dragonfly
  password: mypassword
  database: manager

Credentials from Kubernetes Secret

mysql:
  enable: false
externalPostgres:
  enable: true
  host: my-postgres-host
  database: manager
  username: __PG_USER__
  password: __PG_PASSWORD__
manager:
  renderConfig: true
  extraInitContainers:
    - name: inject-pg-credentials
      image: busybox:latest
      command: ["sh", "-c", "sed 's/__PG_USER__/$PG_USER/g; s/__PG_PASSWORD__/$PG_PASSWORD/g' /etc/dragonfly-template/manager.yaml > /etc/dragonfly/manager.yaml"]
      env:
        - name: PG_USER
          valueFrom:
            secretKeyRef:
              name: my-postgres-secret
              key: username
        - name: PG_PASSWORD
          valueFrom:
            secretKeyRef:
              name: my-postgres-secret
              key: password
      volumeMounts:
        - name: config
          mountPath: /etc/dragonfly-template
        - name: config-rendered
          mountPath: /etc/dragonfly

Follow-up

A more ergonomic externalPostgres.existingSecret pattern (chart-shipped init container that does the substitution automatically) is a natural follow-up and will land in a separate PR once this one merges. That avoids bloating this PR further and keeps the review focused on the core externalPostgres + renderConfig plumbing.

[bumarcell]

Could a maintainer please add the enhancement label? The Classify PR check requires it and I don't have permission to add labels from my fork.

[Copilot]

Pull request overview

This PR updates the Dragonfly Helm chart to support configuring the manager database as external PostgreSQL (in addition to the existing MySQL configuration), and adds a chart value to allow injecting extra init containers into the manager Deployment.

Changes:

• Add externalPostgres configuration to values.yaml and document it in README.md.
• Update manager-configmap.yaml to render database.type and a PostgreSQL config block when enabled.
• Update manager-deployment.yaml to support manager.extraInitContainers and to introduce a config-rendered volume path for PostgreSQL mode.

Reviewed changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 4 comments.

Show a summary per file

File	Description
charts/dragonfly/values.yaml	Adds manager.extraInitContainers and new externalPostgres values.
charts/dragonfly/templates/manager/manager-deployment.yaml	Allows extra init containers; switches manager config mount to config-rendered and adds an emptyDir volume in PostgreSQL mode.
charts/dragonfly/templates/manager/manager-configmap.yaml	Adds PostgreSQL database configuration rendering and database.type.
charts/dragonfly/README.md	Documents externalPostgres values and manager.extraInitContainers.
charts/dragonfly/Chart.yaml	Bumps chart version and updates Artifact Hub changelog annotations.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[bumarcell]

I have this already deployed and running. Please let me know if you find any problem!

[junjieteo]

Will this be merged soon?

[tz-torchai]

Thanks for the PR! Could you also add existingSecret field so d7y directly reads from the K8s secret instead of using init container?

cc: @gaius-qi @jim3ma @chlins @yxxhero @Liam-Zhao for review

[gaius-qi]

@bumarcell Please resolve conflicts.

[bumarcell]

@tz-torchai the initContainer is needed to decide where to pull the creds from, based on the config.
Or did I misunderstand your point?

[bumarcell]

@gaius-qi I don't see any merge conflict (un)fortunately

[tz-torchai]

@tz-torchai the initContainer is needed to decide where to pull the creds from, based on the config. Or did I misunderstand your point?

I see, the cleaner fix would be an app-side PR adding AutomaticEnv() so existingSecret could work via plain secretKeyRef env vars with no init container, but that's dragonflyoss/dragonfly, separate from this chart PR. Not blocking this one.

cc: @gaius-qi @BraveY @imeoer @yxxhero