runner-instance-scope #19
Loading…
Reference in a new issue
No description provided.
Delete branch "runner-instance-scope"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Runner ci-rust was registered under the adicom organization — invisible to jobs from cinnae/* repos (notably cinnae/infrastructure's new build-ci-job-image workflow). Re-registered at instance level via Forgejo UI (Site Administration → Actions → Runners → Create new runner) to serve all orgs on this Forgejo instance. This commit only updates the UUID; the matching Token goes into the existing forgejo-runner-token Secret via kubectl patch (never committed). Rollout (live cluster, do not wait for PR merge): 1. kubectl -n forgejo patch secret forgejo-runner-token \ -p '{"data":{"RUNNER_TOKEN":"<base64-of-new-token>"}}' 2. kubectl apply -f helm/runners/20-configmap.yaml 3. kubectl rollout restart deployment/forgejo-runner -n forgejo 4. Verify in Forgejo UI → Site Administration → Actions → Runners that ci-rust appears with Type=Instance and Status=Idle. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>Two unrelated fixes that both blocked the first Phase C CI deploy on adicom/test-ci: 1. 21-forgejo-deployer-kubeconfig.sh: --embed-certs=true + --raw Without --embed-certs, kubectl stored the temp file PATH in the kubeconfig (not the contents) — broke as soon as the temp file was shredded. Without --raw, kubectl redacts certificate-authority-data to "DATA+OMITTED" which base64-decodes to garbage. The two bugs surfaced sequentially in the deploy job: "unable to read certificate-authority /root/.kube/tmp.XXX" "unable to parse bytes as PEM block" 2. 02-sops-rbac-aggregation.yaml (new): sops-secrets-operator's CRD ships without the aggregate-to-admin annotation, so a RoleBinding to clusterrole=admin does NOT grant CRUD on SopsSecrets. Symptom: Forbidden: cannot get resource "sopssecrets" in API group "isindir.github.com" Fixed by a dedicated aggregation ClusterRole — auto-included in admin/edit going forward. README step 3 documents the apply.