From e57f458058c4e283a6b5d8de37cffd7463e1e980 Mon Sep 17 00:00:00 2001 From: Julia McGhee Date: Sat, 21 Mar 2026 17:14:30 +0000 Subject: [PATCH] Fix runner: use CONFIG_FILE env var instead of command override The command override bypasses the entrypoint that handles registration. Use CONFIG_FILE env var which the entrypoint respects, keeping the registration flow intact. --- infra/kubernetes/platform/gitea-runner/deployment.yaml | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/infra/kubernetes/platform/gitea-runner/deployment.yaml b/infra/kubernetes/platform/gitea-runner/deployment.yaml index d77037c..9633abc 100644 --- a/infra/kubernetes/platform/gitea-runner/deployment.yaml +++ b/infra/kubernetes/platform/gitea-runner/deployment.yaml @@ -18,8 +18,9 @@ spec: containers: - name: runner image: gitea/act_runner:latest - command: ["act_runner", "daemon", "--config", "/config/config.yaml"] env: + - name: CONFIG_FILE + value: /config/config.yaml - name: GITEA_INSTANCE_URL value: http://gitea-helm-http.platform.svc:3000 - name: GITEA_RUNNER_REGISTRATION_TOKEN