From 8dd10b3b860205edf0f1580af1cf2dfc05638563 Mon Sep 17 00:00:00 2001 From: SmokyZone Date: Tue, 20 Oct 2026 11:58:23 +0200 Subject: [PATCH] Gitea: Chart-Admin-Setup abschalten (gitea_admin geloescht, sonst Neuanlage mit Default-Passwort) Co-Authored-By: Claude Opus 5.5 --- values.yaml | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/values.yaml b/values.yaml index 837f248..6a6d5bf 100644 --- a/values.yaml +++ b/values.yaml @@ -144,10 +144,10 @@ applications: # Gitea - Git server for all *-gitops repos (and thus ArgoCD's own source). # Was created by hand with kubectl; now managed here. - # Admin password is NOT stored here: the admin user already exists and - # passwordMode initialOnlyNoReset means the chart never touches it again. - # Change the password in the Gitea UI. (If the data volume is ever lost, the - # chart would recreate gitea_admin with its public default password - change it immediately.) + # No chart-managed admin: the bootstrap user gitea_admin was deleted, the user's + # own account is admin. Empty username+password makes the chart skip + # configure_admin_user entirely - otherwise it would recreate gitea_admin with + # the chart's PUBLIC default password on every pod start. # Careful: if Gitea does not come up, ArgoCD cannot fetch fixes from git either. - name: gitea enabled: true @@ -175,8 +175,8 @@ applications: gitea: admin: - username: gitea_admin - passwordMode: initialOnlyNoReset + username: "" + password: "" config: database: DB_TYPE: sqlite3