Skip to content

feat: add opt-in preservation of secret values across helm upgrade - #199

Open
dhcsousa wants to merge 2 commits into
supabase-community:mainfrom
dhcsousa:feat/preserve-secrets-across-upgrade
Open

feat: add opt-in preservation of secret values across helm upgrade#199
dhcsousa wants to merge 2 commits into
supabase-community:mainfrom
dhcsousa:feat/preserve-secrets-across-upgrade

Conversation

@dhcsousa

Copy link
Copy Markdown

What kind of change does this PR introduce?

Feature (opt-in) + docs.

What is the current behavior?

Closes #198. Self-managed Secrets render from .Values.secret.* (public demo defaults), so a helm upgrade that doesn't re-supply overrides silently reverts live JWT/DB credentials to the demo values.

What is the new behavior?

Adds opt-in secret.preserveExisting (default false). When enabled, each self-managed secret reuses the existing in-cluster values via lookup and gets a helm.sh/resource-policy: keep annotation. Applied to all self-managed secrets (jwt, db, dashboard, smtp, analytics, apikey, meta, minio, realtime, s3, bigquery); secretRef secrets unaffected.

Additional context

helm lint passes; default render unchanged.

@luizfelmach

luizfelmach commented Jul 14, 2026

Copy link
Copy Markdown
Contributor

See #198

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Self-hosted secrets (JWT, DB password, dashboard) silently revert to public demo values on helm upgrade

2 participants