Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Running Gitea Actions runners in Kubernetes cluster #14594

Open
framitdavid opened this issue Feb 6, 2025 · 0 comments
Open

Running Gitea Actions runners in Kubernetes cluster #14594

framitdavid opened this issue Feb 6, 2025 · 0 comments
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.

Comments

@framitdavid
Copy link
Collaborator

framitdavid commented Feb 6, 2025

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.

@framitdavid framitdavid added 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. labels Feb 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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.
Projects
Status: No status
Development

No branches or pull requests

1 participant