Running Gitea Actions runners in Kubernetes cluster #14594
Labels
kind/user-story
Used for issues that describes functionality for our users.
status/draft
Status: When you create an issue before you have enough info to properly describe the issue.
Description
We need to explore the best approach for running the 'act runners' within Kubernetes clusters. We need to determine whether it makes more sense to run them in the Studio Kubernetes cluster or the app-cluster.
The advantage of running the 'act runners' in the app-cluster is that we can allocate the costs to the service owner, but this likely introduces more complexity. The alternative is to host/run them in the Studio cluster, which could potentially increase our costs or require us to develop a model to track usage costs. This needs to be analyzed further, and we need to agree on the next steps
Additional information
Gitea Actions requires act runner to run the jobs. In order to avoid consuming too many resources and affecting the Gitea instance, it is recommended to start runners on separate machines from the Gitea instance.
How
We can use the pre-built binaries or the docker images to set up the runner. Docker image is recommended.
The text was updated successfully, but these errors were encountered: