From 44d8e1e09dad0c76da04ee7b8500b01decaaf56c Mon Sep 17 00:00:00 2001 From: rock Date: Sun, 6 Sep 2026 22:26:01 -0700 Subject: [PATCH] fix: always re-register runner to keep labels in sync with values.yaml MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Init container skipped registration if .runner file existed on PVC. Changing labels in values.yaml had no effect until PVC was manually deleted — not GitOps-friendly. Fix: rm -f .runner and re-register on every pod start. --- k8s/infra/forgejo-runner/templates/deployment.yaml | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/k8s/infra/forgejo-runner/templates/deployment.yaml b/k8s/infra/forgejo-runner/templates/deployment.yaml index f60ab36..2ef614f 100644 --- a/k8s/infra/forgejo-runner/templates/deployment.yaml +++ b/k8s/infra/forgejo-runner/templates/deployment.yaml @@ -34,7 +34,11 @@ spec: command: ["sh", "-c"] args: - | - test -f /data/.runner || forgejo-runner register --no-interactive \ + # Always re-register to keep labels in sync with values.yaml. + # Without this, changing a runner label requires manually deleting + # the PVC or .runner file — not GitOps-friendly. + rm -f /data/.runner + forgejo-runner register --no-interactive \ --instance {{ .Values.runner.forgejoUrl }} \ --token $(RUNNER_TOKEN) \ --name {{ .Values.runner.name }} \