add replicas to act-runner #726

Closed
opened 2024-11-12 07:23:49 +00:00 by evanrich · 2 comments
evanrich commented 2024-11-12 07:23:49 +00:00 (Migrated from gitea.com)

The act-runner stateful set only deploys a single replica, there isn't even a "replicas" config section.

The act-runner stateful set only deploys a single replica, there isn't even a "replicas" config section.
kingphil commented 2024-11-12 23:06:25 +00:00 (Migrated from gitea.com)

I was in this vicinity earlier today. Concurrency is handled in the runner config as capacity!

actions:
  enabled: true
  statefulset:
    actRunner:
      config: |
        runner:
          capacity: 4

This should be more prominently documented! I only noticed this by digging:
https://gitea.com/gitea/act_runner/src/branch/main/internal/pkg/config/config.example.yaml#L14

I was in this vicinity earlier today. Concurrency is handled in the runner config as `capacity`! ``` actions: enabled: true statefulset: actRunner: config: | runner: capacity: 4 ``` This should be more prominently documented! I only noticed this by digging: https://gitea.com/gitea/act_runner/src/branch/main/internal/pkg/config/config.example.yaml#L14
evanrich commented 2024-11-13 04:31:03 +00:00 (Migrated from gitea.com)

@kingphil you're a life saver! I was using a custom helm chart that did basically the same thing, but spun up multiple runners, this is a suitable alternative! thanks for commenting, I'll close this as it solves the issue.

@kingphil you're a life saver! I was using a custom helm chart that did basically the same thing, but spun up multiple runners, this is a suitable alternative! thanks for commenting, I'll close this as it solves the issue.
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: lunny/helm-chart#726
No description provided.