avoid idle runners after 30 minutes

Author: mirkoSekulic

charts/gitea-org-runner/templates/scaledjob.yaml

@@ -18,6 +18,12 @@ spec:
   jobTargetRef:
     backoffLimit: 0
     ttlSecondsAfterFinished: {{ $.Values.keda.ttlSecondsAfterFinished | default 300 }}
+    # Cap on total Job runtime. Without this, a runner pod that registers
+    # but never gets dispatched a workflow polls Gitea forever (act_runner
+    # has no built-in idle timeout). Set generously enough that legitimate
+    # long workflows can finish, but short enough that orphaned idle
+    # runners get reaped.
+    activeDeadlineSeconds: {{ $.Values.keda.activeDeadlineSeconds | default 1800 }}
     template:
       metadata:
         labels:

charts/gitea-org-runner/values.yaml

@@ -89,6 +89,11 @@ keda:
   pollingInterval: 30
   # KEDA cleans up completed Jobs older than this many seconds.
   ttlSecondsAfterFinished: 300
+  # Hard cap on total Job runtime. Pod is killed if it exceeds this even
+  # while polling for work. Set to a value larger than the longest legitimate
+  # workflow you expect. Default 1800 = 30 min; raise if workflows can run
+  # longer, lower if you want orphaned idle runners reaped faster.
+  activeDeadlineSeconds: 1800
   # K8s keeps the last N successful / failed Job records visible.
   successfulJobsHistoryLimit: 5
   failedJobsHistoryLimit: 5