Helm: Add ability to pass an existing secret in for Database URI Fiel #504

New Issue

OVERLORD · 2026-02-04T19:58:27+03:00

OVERLORD commented

2026-02-04 19:58:27 +03:00

Originally created by @justmitch123 on GitHub (May 10, 2024).

We would like to be able to pass secrets into the pods as Kubernetes secret values rather than plaintext env values.

The current helm chart forces a value for dburl which makes for a difficult Kustomize patch to replace this.

The proposal is to edit the deployment chart to include

  valueFrom:
    secretKeyRef:
      name: .Values.existingDburlSecret
      key: uri

as a valid database connection string.

It is possible to work around this issue with merge patches to replace the env variables, but it would be good to remove these Kustomize overlays if possible

Originally created by @justmitch123 on GitHub (May 10, 2024). We would like to be able to pass secrets into the pods as Kubernetes secret values rather than plaintext env values. The current helm chart forces a value for `dburl` which makes for a difficult Kustomize patch to replace this. The proposal is to edit the deployment chart to include ``` valueFrom: secretKeyRef: name: .Values.existingDburlSecret key: uri ``` as a valid database connection string. It is possible to work around this issue with merge patches to replace the env variables, but it would be good to remove these Kustomize overlays if possible

OVERLORD closed this issue

2026-02-04 19:58:37 +03:00

OVERLORD referenced this issue

2026-02-04 21:45:05 +03:00

[PR #504] [MERGED] Fixed turkish translations linting errors #1027

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/planka#504