From 13343976e4988659cc51c788dce778b6220c3347 Mon Sep 17 00:00:00 2001 From: rock Date: Wed, 28 Oct 2026 02:18:29 -0700 Subject: [PATCH] fix(forgejo): the chart key is gitea.podAnnotations, not podAnnotations MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The gitea chart reads pod annotations from gitea.podAnnotations (values.yaml line 583). A top-level key is silently ignored, so the previous commit changed nothing — the Deployment came back without the annotation and Reloader still had no trigger. --- k8s/bootstrap/phase3-forgejo/forgejo-values.yaml | 16 ++-------------- 1 file changed, 2 insertions(+), 14 deletions(-) diff --git a/k8s/bootstrap/phase3-forgejo/forgejo-values.yaml b/k8s/bootstrap/phase3-forgejo/forgejo-values.yaml index cf6d45a..5df79e3 100644 --- a/k8s/bootstrap/phase3-forgejo/forgejo-values.yaml +++ b/k8s/bootstrap/phase3-forgejo/forgejo-values.yaml @@ -34,6 +34,8 @@ service: lbipam.cilium.io/ips: "192.168.1.161" gitea: + podAnnotations: + reloader.stakater.com/auto: "true" admin: existingSecret: forgejo-admin @@ -102,20 +104,6 @@ persistence: accessModes: - ReadWriteOnce -# Pod annotations. -# -# GITEA__DATABASE_PASSWD comes from forgejo-db-app, a Secret the CNPG Cluster CR owns -# and generates: cloudnative-pg created it, and there is no bootstrap secret, so -# nothing else knows that password. The Deployment reads it into the environment at -# start, so a regenerated password would leave Forgejo authenticating with a value the -# database no longer accepts — the pod stays up and every query fails. -# -# The cnpg.io/reload label on the Secret is only a hint. This annotation is what makes -# Stakater Reloader restart the pod when the Secret changes, so the environment is -# refreshed instead of silently stale. -podAnnotations: - reloader.stakater.com/auto: "true" - # Ingress ingress: enabled: true