Init container skips registration if .runner file exists on PVC:
test -f /data/.runner || forgejo-runner register ...
This means changing runner labels in values.yaml (e.g. the label image fix from PR #1) has no effect until PVCs are manually deleted — not GitOps-friendly.
Fix
Always delete .runner and re-register on every pod start:
ArgoCD syncs → deployment spec changes → pods restart → init re-registers with new labels from PR #1 → CI works across all repos.
## Problem
Init container skips registration if `.runner` file exists on PVC:
```
test -f /data/.runner || forgejo-runner register ...
```
This means changing runner labels in `values.yaml` (e.g. the label image fix from PR #1) has **no effect** until PVCs are manually deleted — not GitOps-friendly.
## Fix
Always delete `.runner` and re-register on every pod start:
```
rm -f /data/.runner
forgejo-runner register --no-interactive ...
```
Labels now stay in sync with `values.yaml` automatically. ArgoCD syncs → pods restart → init re-registers with current labels.
## Files Changed
- `k8s/infra/forgejo-runner/templates/deployment.yaml` (init container logic)
## After Merge
ArgoCD syncs → deployment spec changes → pods restart → init re-registers with new labels from PR #1 → CI works across all repos.
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.
rock
changed title from fix: Forgejo CI runners + CoreDNS api.riotpiao.com rewrite to fix: always re-register runner to keep labels in sync2026-09-07 05:26:16 +00:00
rock
merged commit 326be2e057 into main2026-09-07 05:27:32 +00:00
rock
deleted branch fix/ci-runners-and-dns2026-09-07 05:27:33 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Problem
Init container skips registration if
.runnerfile exists on PVC:This means changing runner labels in
values.yaml(e.g. the label image fix from PR #1) has no effect until PVCs are manually deleted — not GitOps-friendly.Fix
Always delete
.runnerand re-register on every pod start:Labels now stay in sync with
values.yamlautomatically. ArgoCD syncs → pods restart → init re-registers with current labels.Files Changed
k8s/infra/forgejo-runner/templates/deployment.yaml(init container logic)After Merge
ArgoCD syncs → deployment spec changes → pods restart → init re-registers with new labels from PR #1 → CI works across all repos.
ad1ce5e4aato44d8e1e09dfix: Forgejo CI runners + CoreDNS api.riotpiao.com rewriteto fix: always re-register runner to keep labels in sync