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.

Sign up for GitHub

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

Jump to bottom

Set Up Self-Hosted Kubernetes Runners #185

Open
CodeGat opened this issue Dec 16, 2024 · 0 comments
Open

Set Up Self-Hosted Kubernetes Runners #185

CodeGat opened this issue Dec 16, 2024 · 0 comments
Assignees
@CodeGat
Labels
CI 2.0 Relating to the second iteration of build-ci priority:high A high priority issue - has an impact on core functionality type:feature New feature or request

Comments

@CodeGat
Copy link
Member

CodeGat commented Dec 16, 2024 •
edited
Loading

The more model components, models and configurations we support, the more runners that we will need - especially when these runners are running quite intensive, long jobs. Eventually, this could lead to jobs being blocked as there are not enough runners for the organization.

Set up a Kubernetes cluster that utilizes https://github.com/actions/actions-runner-controller on a Nirin instance. In this first instance, no secrets are allowed on jobs that use self-hosted.

See ACCESS-NRI/build-cd#2
@CodeGat CodeGat added CI 2.0 Relating to the second iteration of build-ci priority:high A high priority issue - has an impact on core functionality type:feature New feature or request labels Dec 16, 2024
@CodeGat CodeGat self-assigned this Dec 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@CodeGat CodeGat

Labels
CI 2.0 Relating to the second iteration of build-ci priority:high A high priority issue - has an impact on core functionality type:feature New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@CodeGat