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

github-runner support for GitHub Runner Groups #5853

Closed
rdvansloten opened this issue Jun 2, 2024 · 3 comments
Closed

github-runner support for GitHub Runner Groups #5853

rdvansloten opened this issue Jun 2, 2024 · 3 comments
Labels
feature-request All issues for new features that have not been committed to needs-discussion stale All issues that are marked as stale due to inactivity

Comments

@rdvansloten
Copy link

Proposal

My organization is using Runner Groups to filter GitHub workflow jobs/tasks into different private runners, but by default only a preset list of repos or ent/org is supported, where KEDA will trigger on all jobs pending for the entire org. I haven't found a way to scope it to a specific Runner Group. I am not sure if the base URL "api.github.com" can be adjusted to include a path/arg as a workaround, but I couldn't find much about what precise call KEDA does to what/where.

Use-Case

We're intending to use this in conjunction with Azure's Container Apps Jobs (A few Kubernetes jobs in a trench coat):
https://learn.microsoft.com/en-us/azure/container-apps/tutorial-ci-cd-runners-jobs?tabs=bash&pivots=container-apps-jobs-self-hosted-ci-cd-azure-pipelines

So the flow without being to scope to Runner Groups would be:
GitHub Job pending -> KEDA in all my environments respond to org-wide Job pending -> all Container App Jobs in all my environments go +1

Desired outcome:
GitHub Job pending for RunnerGroupABC -> KEDA in environment ABC responds to Job pending -> Container App Job in environment ABC goes +1

Is this a feature you are interested in implementing yourself?

No

Anything else?

No response

@rdvansloten rdvansloten added feature-request All issues for new features that have not been committed to needs-discussion labels Jun 2, 2024
@KoblerS
Copy link
Contributor

KoblerS commented Jun 12, 2024

wouldn't it work if you use labels for labeling your workflow runsOn?

runs-on:
  group: org/my-group
  labels: [ self-hosted, my-group]

Copy link

stale bot commented Aug 11, 2024

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale All issues that are marked as stale due to inactivity label Aug 11, 2024
Copy link

stale bot commented Aug 28, 2024

This issue has been automatically closed due to inactivity.

@stale stale bot closed this as completed Aug 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request All issues for new features that have not been committed to needs-discussion stale All issues that are marked as stale due to inactivity
Projects
None yet
Development

No branches or pull requests

2 participants