From af9f013c5e695c58607375603de164840bd1775d Mon Sep 17 00:00:00 2001 From: Maurice Date: Tue, 13 Oct 2026 21:10:41 +0200 Subject: [PATCH] docs(chart): NOTES lists every key the chart reads from existingSecret SMTP_PASS, MAPBOX_ACCESS_TOKEN, CARTO_API_KEY and DEMO_ADMIN_PASS were read but missing from the install notes; values.yaml already listed them. --- charts/trek/templates/NOTES.txt | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/charts/trek/templates/NOTES.txt b/charts/trek/templates/NOTES.txt index 8c70022a4..7845bc00d 100644 --- a/charts/trek/templates/NOTES.txt +++ b/charts/trek/templates/NOTES.txt @@ -5,8 +5,9 @@ - To use an existing Kubernetes secret, set `existingSecret` to the secret name. The chart then renders no Secret of its own and reads every secret env var from that secret: `ENCRYPTION_KEY` (renamable via `existingSecretKey`), plus `ADMIN_EMAIL`, `ADMIN_PASSWORD`, `OIDC_CLIENT_SECRET`, - `UNSPLASH_ACCESS_KEY`, `PLACES_API_KEY`, `AMAP_API_KEY`, `AMAP_API_SECRET` and - `VAPID_PRIVATE_KEY`. Missing keys are simply left unset, so only provide the ones you use. + `UNSPLASH_ACCESS_KEY`, `PLACES_API_KEY`, `AMAP_API_KEY`, `AMAP_API_SECRET`, + `VAPID_PRIVATE_KEY`, `SMTP_PASS`, `MAPBOX_ACCESS_TOKEN`, `CARTO_API_KEY` and + `DEMO_ADMIN_PASS`. Missing keys are simply left unset, so only provide the ones you use. - If left empty, the server resolves the key automatically: existing installs fall back to data/.jwt_secret (encrypted data stays readable with no manual action); fresh installs auto-generate a key persisted to the data PVC.